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

@kobayami/env-utils

v1.0.0

Published

Utilities for multi-platform code that runs in Web and NodeJS environments.

Downloads

4

Readme

@kobayami/env-utils

Installation

npm install --save @kobayami/env-utils

Version and License

Summary

Utilities for multi-platform code that runs in Web and NodeJS environments:

  • Check for environment type (NodeJS or Web)
  • Enable dynamic NodeJS module loading during runtime (i.e., not via static import statements)
  • WebPack compatibility

Usage Example

Dynamically loads a NodeJS module during runtime. Throws an exception if the code is not running in a NodeJS environment. This can also be safely embedded into code running in a Web environment like this:

if (envType === EnvType.NODE) {
    const leModule = requireNodeModuleAtRuntime('leModule');
    leModule.foo();
    ...
}

This is a practical example from @kobayami/threads:

const WorkerClass = envType === EnvType.NODE?
    requireNodeModuleAtRuntime('worker_threads').Worker: Worker

For multi platform code, this approach is sometimes necessary, because NodeJS specific modules must only be loaded after we have confirmed that we are not running in a Web environment. A simple import at the beginning of a file would therefore not work, browsers would raise a 404 error.

Module loading via this function is also compatible with WebPack, which is the actual reason why we need it as a wrapper for the NodeJS require function. When your code is being bundled and packaged by WebPack, dynamic module loading via this approach does not confuse WebPack. No additional configuration is necessary.

See Also