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

atlasai-carto-react

v0.0.3

Published

## Artifact Registry

Downloads

6

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

ionutrusuionutrusu

Keywords

Readme

CARTO React Library

Artifact Registry

Set up Credential Helper

Only do this once locally. Note the scope so that we can publish and install packages from the correct repository

gcloud auth login --update-adc

gcloud artifacts print-settings npm \
    --project=swe-prod-415921  \
    --repository=carto \
    --location=us-west1 \
    --scope=@carto >> ./.npmrc

Obtain an Access Token

Access tokens are only valid for 60 minutes. So you will need to run the following often

yes | yarn artifactregistry-login

If there are any errors, your GCP credentials may have expired

gcloud auth login --update-adc

Publish

Basic command to publish to Artifact Registery may look like

npm publish @carto/SOMETHING

References

  • https://cloud.google.com/artifact-registry/docs/nodejs
  • https://cloud.google.com/artifact-registry/docs/nodejs/authentication

--

This is the official "CARTO for React library". It is organized as a set of npm packages (@carto/react-*), that work together providing widgets and utilities to build Location Intelligence applications with React, Redux & Material-UI.

The packages are:

To work in the code, see developers.

These packages are used by the CARTO for React templates, made with CRA (Create React App).

There is a Storybook guide with the main UI components and how to use them at CARTO for React - UI Components

How to install the library

If you are using the CARTO CRA templates, everything is already setup, so no further configuration is needed!

In case you want to use this set of packages in a different context, then you would need to install them as usual, with something like:

  yarn add @carto/react-api
  yarn add @carto/react-auth
  yarn add @carto/react-basemaps
  yarn add @carto/react-core
  yarn add @carto/react-redux
  yarn add @carto/react-ui
  yarn add @carto/react-widgets
  yarn add @carto/react-workers

Notice that to avoid issues within host projects, most of the base libraries are declared as peer dependencies (deck.gl, react, material-ui, reduxjs-toolkit, echarts...). That means that you would need to add them explicitly to your project, if you are still not using them (keep an eye on the console warnings on peer dependencies).