npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@locio-au/react

v0.2.0

Published

React address autocomplete for Australian addresses: validation, autocomplete and geocoding from G-NAF

Readme

@locio-au/react

React address autocomplete for Australian addresses, with validation and geocoding built in. Backed by G-NAF, the national address register.

  • An accessible combobox you can drop in, or a headless hook if you have your own markup
  • Debounced and cancelled properly, so typing an address costs one request rather than thirteen
  • Every result is already resolved: a stable G-NAF id, a coordinate, an ABS mesh block and the address split into fields. No second call to find out what was picked.
  • No dependencies beyond React
npm install @locio-au/react

Quick start

import { AddressAutocomplete, addressId } from "@locio-au/react";

export function Checkout() {
  return (
    <AddressAutocomplete
      publicKey="lc_pub_..."
      label="Delivery address"
      onSelect={(address) => {
        console.log(address.formatted);
        console.log(addressId(address)); // store this, not the text
        console.log(address.lat, address.lng);
        console.log(address.components?.postcode);
      }}
    />
  );
}

That is the whole integration. It handles the debounce, cancels superseded requests, and implements the ARIA combobox pattern so arrow keys, Enter and Escape all work.

Use a public key

lc_pub_..., created at locio.com.au/account/api. A public key carries an origin allow list, so a copy lifted from your page does nothing anywhere else.

Never put a secret key (lc_live_...) in a page. Anyone who opens it can read the key and spend your quota. This package throws at construction if it sees a secret key in a browser rather than letting it reach production working perfectly.

For server code use locio (Python) or locio-go.

Styling

The default styles are deliberately minimal. Replace them with your own class names:

<AddressAutocomplete
  publicKey="lc_pub_..."
  classNames={{
    root: "relative",
    input: "w-full rounded-md border px-3 py-2",
    list: "absolute z-10 w-full rounded-md border bg-white shadow",
    option: "px-3 py-2 hover:bg-neutral-100",
    status: "text-xs text-neutral-500",
  }}
/>

Or take the markup bare with styled={false}.

Headless

If you want your own markup entirely, the hook has all the behaviour and no opinion about the DOM:

import { useAddressAutocomplete, addressId } from "@locio-au/react";

function MyField() {
  const { term, setTerm, results, status } = useAddressAutocomplete({
    publicKey: "lc_pub_...",
    debounceMs: 300,
    minLength: 3,
  });

  return (
    <>
      <input value={term} onChange={(e) => setTerm(e.currentTarget.value)} />
      {status === "searching" && <span>Searching…</span>}
      {status === "empty" && <span>No addresses match that yet.</span>}
      {status === "unavailable" && <span>Lookup is unavailable.</span>}
      <ul>
        {results.map((a) => (
          <li key={addressId(a)}>{a.formatted}</li>
        ))}
      </ul>
    </>
  );
}

status is one value rather than several booleans, because "searching" and "nothing found" being separately true is how a widget ends up claiming both.

Note that empty and unavailable are different states. A widget that renders nothing for both tells the user neither, and an outage then looks exactly like an address that does not exist.

Address validation on its own

The client is exported if you want the other calls without the UI:

import { createClient, addressId } from "@locio-au/react";

const locio = createClient({ publicKey: "lc_pub_..." });

const result = await locio.resolve("1 george st sydenham nsw 2044");
if (result.matched) {
  console.log(addressId(result.address!));
}

search, resolve and get cost one unit; similar costs three.

Where your visitor is

A public key is scoped to the country the visitor is in, which the service resolves from their own connection. Nothing in a page can widen that, and it is why the key is safe to publish.

So a visitor in a country we hold no addresses for gets no results and a sentence saying why, as an ordinary answer that costs nothing. Show that sentence rather than your own "nothing matched" message, which was written for somebody who has not typed enough yet:

const { results, status, note, countryCode } = useAddressAutocomplete({
  publicKey: "lc_pub_...",
});
// status === "empty" && note
//   -> "we hold no address data for NZ. Addresses are available for AU."

<AddressAutocomplete /> already does this: when the service explains itself, its message is the one shown. searchScoped and similarScoped on the client return the same three things without the UI.

Australia is what is covered today.

Which id to store

Read the id through addressId(address). It is the address's id in its country's register, and the one field every address carries:

| Field | Means | |---|---| | id | This address. The one to store. Read it through addressId. | | address_detail_pid | The same id, under G-NAF's own column name. Australian addresses only. | | gnaf.primary_pid | The parcel it sits on, when the row is a unit. Australian addresses only. |

An address outside Australia carries id and country_code and none of the G-NAF fields: no pid, no mesh_block, no gnaf object. They are absent rather than empty, because an empty one would say we hold something we do not. Ids are unique within a country, so store country_code beside the id.

import { isUnit } from "@locio-au/react";

Storing the primary pid stores the building rather than the door, and nothing about the value itself says which you have.

Props

| Prop | Default | | |---|---|---| | publicKey | — | Required. lc_pub_... | | label | "Address" | Visible label, also names the suggestion list | | placeholder | "Start typing an address" | | | onSelect | — | Called with the picked Address | | debounceMs | 300 | Quiet time before a request | | minLength | 3 | Characters before anything is requested | | limit | service default | How many candidates to ask for | | classNames | — | root, label, input, list, option, status | | styled | true | false for bare markup | | baseUrl | https://api.locio.com.au | For a proxy of your own |

Accessibility

Implements the ARIA combobox pattern: role="combobox" with aria-expanded, aria-controls and aria-activedescendant; a role="listbox" of role="option"; arrow keys, Enter and Escape. The input is 16px, because anything smaller makes iOS zoom the page on focus.

Licence

MIT. Address data is G-NAF, published by Geoscape Australia under CC BY 4.0; attribution belongs wherever you show it.