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

@anil-labs/google-places-autocomplete-core

v0.2.0

Published

Framework-agnostic engine for Google Places Autocomplete (New): debounced predictions, session-token billing, keyboard navigation and place-details resolution — zero runtime dependencies.

Readme

@anil-labs/google-places-autocomplete-core

Framework-agnostic engine for Google Places Autocomplete (New): debounced predictions, automatic session-token billing, keyboard navigation and place-details resolution. Zero runtime dependencies — talks to places.googleapis.com with plain fetch, no Maps JavaScript SDK, no global namespace.

This is the shared engine behind @anil-labs/google-places-autocomplete-vue, -react, -svelte, -solid and -element. Install one of those directly unless you're building your own binding.

Install

npm install @anil-labs/google-places-autocomplete-core

Usage

import { createPlacesAutocomplete } from '@anil-labs/google-places-autocomplete-core'

const controller = createPlacesAutocomplete({
  apiKey: 'YOUR_API_KEY',
  onSelect: (place, suggestion) => console.log(place.formattedAddress),
})

controller.subscribe(() => {
  const state = controller.getState()
  // state.query, state.suggestions, state.status, state.isOpen, ...
})

controller.setQuery('1600 amphi')

See the full API reference and the getting started guide (Google Cloud setup, key restriction).

CDN / no bundler

A standalone build is published for plain <script>-tag use, exposing the engine as window.GooglePlacesAutocompleteCore:

<script src="https://unpkg.com/@anil-labs/google-places-autocomplete-core"></script>
<link rel="stylesheet" href="https://unpkg.com/@anil-labs/google-places-autocomplete-core/styles.css" />
<script>
  const controller = GooglePlacesAutocompleteCore.createPlacesAutocomplete({ apiKey: 'YOUR_API_KEY' })
</script>

For a ready-made UI without wiring the engine yourself, prefer @anil-labs/google-places-autocomplete-element, whose CDN build bundles this engine in and auto-registers a <gpa-autocomplete> tag.

Why this over the legacy Autocomplete widget?

  • No Maps JS SDK — plain fetch, works anywhere fetch/AbortController/crypto.randomUUID() exist.
  • Correct session billing by default — Autocomplete + Place Details share one session token automatically.
  • Bring your own key handling — pass apiKey directly, or override fetcher to proxy through your own backend.

See Session tokens & billing for the full detail.

Styling

./styles.css provides a minimal, CSS-custom-property-based baseline (.gpa-root, .gpa-input, .gpa-panel, .gpa-listbox, .gpa-option, .gpa-status, .gpa-empty) shared by every wrapper package:

import '@anil-labs/google-places-autocomplete-core/styles.css'

Override the custom properties (--gpa-bg, --gpa-fg, --gpa-accent, etc.) on .gpa-root to theme.

License

MIT © Er. Anil Kumar Thakur