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

datastore-emulator-enforcer

v1.0.3

Published

Simple tool to ensure google-cloud datastore targets an emulator, to avoid pollution of production data.

Downloads

14

Readme

datastore-emulator-enforcer

Dead simple tool to make sure @google-cloud/datastore will target an emulator, so that tests/development won't pollute your production datastore.

To use it, simply require it before @google-cloud/datastore, e.g.

if (process.env.NODE_ENV !== 'production') {
  require('datastore-emulator-enforcer');
}

var myDatastore = require('@google-cloud/datastore')(/* init options */);

The enforcer throws an error if:

  • @google-cloud-datastore was required before the enforcer (i.e. datastore might already be pointing to production)
  • The emulator environment variables were not already present, and they could not be automatically determined & set.

If process.env does not already contain all emulator env vars, the enforcer will try to set them by running gcloud beta emulators datastore env-init. However, it won't override already-specified values.

  • Auto-determining emulator env vars only works if you're running a local emulator. You need to have installed the Google Cloud SDK
  • This functionality won't work if you're using the emulator on another host (, docker image, etc) – in that case, env vars must be specified ahead of time.

License

ISC