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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@traveltech/react-loqate

v3.0.2

Published

This is a React implementation of the loqate APIs. It features an input, typing in which will result in a list of address options. Clicking an option will trigger your callback with that option.

Downloads

36

Readme

React-Loqate

This is a React implementation of the loqate APIs. It features an input, typing in which will result in a list of address options. Clicking an option will trigger your callback with that option.

Usage

Notes

You must polyfill fetch.

Installation

npm install react-loqate

Example

import AddressSearch from 'react-loqate';
// to use the default styles for the default components
import 'react-loqate/dist/index.css';

// ...
<AddressSearch
  locale="en-GB"
  apiKey="AA11-AA11-AA11-AA11"
  onSelect={(address) => console.log(address)}
/>;
// ...

Props

| name | type | required | example | description | | ---------- | ----------------------------------------------------- | -------- | ------------------------------------------------------------------- | ---------------------------------------- | | apiKey | string | yes | "AA11-AA11-AA11-AA11" | Loqate API key | | locale | string | yes | "en-GB" | Language to be used | | onSelect | (address) => void | yes | address => console.log(address) | Callback with for Loqate response | | countries | string[] | no | ["GB", "NL"] | Countries to search in | | limit | number | no | 10 | Number of options to show | | classes | { input?: string, list?: string, listItem?: string} | no | { list: 'list' } | Classnames for the components | | components | see Customization | no | { Input: CustomInput, List: CustomList, ListItem: CustomListItem, } | Components to overwrite the default ones | | inline | boolean | no | true | Render results inline with the input | | debounce | number | no | 100 | Debounce the calls to the Loqate API |

Customization

You can either style the default input, list and listitem with their respective classes or replace them completely by passing in your own components in the components prop.

Custom Input and List components must forward a ref!

All custom components must pass down their props!

import React from 'react';
import AddressSearch from 'react-loqate';

<AddressSearch
  // ...
  components={{
    List: forwardRef(({ className, ...rest }, ref) => (
      <ul
        className={clsx('react-loqate-default-list', className)}
        ref={ref}
        // ...
        {...rest}
      />
    )),
    ListItem: ({ suggestion, ...rest }) => (
      <li
        onKeyDown={(e) => {
          if (e.key === 'ArrowDown') {
            e.preventDefault();
            const next = e.target.nextSibling;
            if (next) {
              next.focus();
            }
          }
          if (e.key === 'ArrowUp') {
            e.preventDefault();
            const previous = e.taget.previousSibling;
            if (previous) {
              previous.focus();
            }
          }
        }}
        {...rest}
      >
        `${suggestion.Text} ${suggestion.Description}`
      </li>
    ),
  }}
  classes={{ Input: classes.input }}
/>;

Errors

Two types of errors can be thrown, LoqateError and ReactLoqateError. Loqate Errors are errors from the Loqate API. Their structure, causes and resolutions can be found in the loqate docs.

Currently only one ReactLoqateError can be thrown. This error occurs when the Retrieve API returns an empty Items array after querying it with an existing ID.

It is on you as the implementing party to catch and handle these errors.

Contributing

This codebases use @changesets for release and version management

  • Create a feature branch with new features / fixes
  • When your code changes are complete, add a changeset file to your feature branch using pnpm changeset
  • Create a PR to request your changes to be merged to main
  • After your PR is merged, GitHub actions will create a release PR or add your changeset to an existing release PR
  • When the release is ready merge the release branch. A new version will automatically be released.