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

node-globals

v0.1.5

Published

immutable namespaced globals for node, main and worker threads

Downloads

61

Readme

Globals!

  • immutable namespaced globals for isomoprhic and progressive web applications
  • Constants management and logic for node, client, and worker threads

why are we here?

  • dont you hate importing and requiring your constants and lib functions all over the friggin place?
    • include namespaced constants and functions one time:
      • on the server, e.g. server.js
      • in the main client thread, e.g. client.js
      • in worker thread, e.g. rootWorker.js
    • on the client main thread: window.appFuncs.somefunction (or just appFuncs.blah)
    • on the client worker thread: self.appConsts.someconst (or just appConsts.blah)
    • in node: global.appFuncs.someFunc (or just appFuncs)

Including globals

  • at the top of the appropriate file:
  const setGlobals = require('node-globals').default;
  setGlobals({});
  // or setGlobals({ constants: {...} }) // add or override default constants
  // or setGlobals({ functions: {...} }) // add or override default functions
  // or setGlobals({ constants: {...}, functions: {...} })
  • or without creating a variable, merging process.env variables within your constants, and storing your constants in a some/directory/config.js
  require('node-globals').default({
    constants: Object.assign(
      { nodeOnline: process.env.NODE_ONLINE === 'true' }, require('../config.js').constants
    )
  });

thank me later...