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

opencage-api-client

v1.0.4

Published

An OpenCageData Geocoder API client library for node and browsers (UMD)

Downloads

7,781

Readme

opencage-api-client

Version Downloads GitHub license Maintained

This repository is an OpenCage Geocoding API client for JavaScript and node.

Continuous integration

CircleCI (all branches) codecov Maintainability Reviewed by Hound

Security

| Source | Scores | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Meterian | stability status security status | | FOSSA | FOSSA Status | | Snyk | Known Vulnerabilities |

Tutorial

You can find a comprehensive tutorial for using this module on the OpenCage site.

🔧 Getting started

Signup for a free-trial API Key.

node

The library uses dotenv on node runtime to configure OpenCage Geocoding API key. But using key as an input parameter is always a possiblity.

First install the library with npm or yarn:

$ npm i --save opencage-api-client

or

$ yarn add opencage-api-client

Create a .env file with:

OPENCAGE_API_KEY=YOUR-OPENCAGE_DATA_API_KEY

Here is an example:

const opencage = require('opencage-api-client');

opencage
  .geocode({ q: 'lyon' })
  .then((data) => {
    console.log(JSON.stringify(data));
  })
  .catch((error) => {
    console.log('error', error.message);
  });

browser

The browser version is built over the node one, obviously without the dotenv feature.

The library is available with unkpg CDN : https://unpkg.com/opencage-api-client

1- include the library:

<!-- latest version -->
<script src="https://unpkg.com/opencage-api-client"></script>
<!-- specific version -->
<script src="https://unpkg.com/[email protected]/dist/opencage-api.min.js"></script>

2- use it

opencage
  .geocode({ q: 'lyon', key: 'YOUR-API-KEY' })
  .then((data) => {
    console.log(JSON.stringify(data));
  })
  .catch((error) => {
    console.log('Error caught:', error.message);
  });

3- others Examples

Found some examples in the examples folder.

✨ API

geocode

| Parameter | Type | Optional? | Description | | --------- | ------ | --------- | --------------------------------------------------------------------------------------------------------- | | q | String | mandatory | the query string to be geocoded: a placename, address or coordinates as lat,long | | key | String | optional | the key can be omitted when using a proxyURL or when using node with a dedicated environment variable | | proxyURL | String | optional | The proxy URL parameter (useful to hide your API key) |

Error handling

API can return errors like invalid key, to many requests, daily quota exceeded, etc. Thoses errors are thrown as Javascript Error by the geocode function. The error object contains the same status object as the OpenCage API.

Assuming the catch statment uses error as variable name:

console.log('Error caught:', error.message);

will output for a 429:

Error caught: Too Many Requests

and

console.log(JSON.stringify(error, null, 2));

will output for a 429:

{
  "status": {
    "code": 429,
    "message": "Too Many Requests"
  }
}

Check the examples using the Test API key from OpenCage error handling examples

🔨 Build and test

  1. Fork or clone this repository
  2. $ cd into the repository folder
  3. $ npm install to install all the required dependencies from npm
  4. lint and test coverage using $ npm test
  5. Build : $ npm run build

🛣 Revision History

Check the CHANGELOG file.

🥂 Contributing

Anyone and everyone is welcome to contribute.

🐞 Issues

Find a bug or want to request a new feature? Please let me know by submitting an issue.

🗝 Licensing

Licensed under the MIT License

A copy of the license is available in the repository's LICENSE file.