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

modlib

v1.2.12

Published

Tool functions to use ES6 modules as npm packages without transpiling

Downloads

17

Readme

ModLib

Use ES6 modules from npm in webapps without transpiling.

ModLib is a tool class, to create a library out of the ES6 modules of node_modules packages to use them in web apps.

The problem with ES6 and npm in web projects

Let's assume we have two ES6 projects. "cm-main" and "cm-dependency" with the following structure: cm-main/src/Main.js and cm-dependency/src/Dependency.js.

When developing "cm-main" the import path from src/Main.js to node_modules/cm-dependency/src/Dependency.js would be ../node_modules/cm-dependency/src/Dependency.js but later when both are npm packages, they are both in node_modules and then the import path will become ../../cm-dependency/Dependency.js. Because of that importing files from node_modules does not work for ES6 web-projects.

The solution (without transpiling)

When we copy node_modules/cm-dependency/src/Dependency.js to lib/Dependency.js on npm install, the include path for local development from src/Main.js will be ../lib/Dependency.js. And later, when both are npm packages, the import path from lib/Main.js will remain ../lib/Dependency.js. 👍

Usage

ModLib is mainly used in postinstall.cjs.

// Create an instance of `ModLib` in your `postinstall.cjs`:

const modLib = new (require("modlib"))

// Then add modules from packages

modLib.add("npm-package-name-1")
modLib.add("npm-package-name-2")
// [..]

The module sources will be copied from the node_modules/package/src/* to the lib/package/* folder for easy handling of the relative import path from other ES6 modules.

Auto execute postinstall.cjs on npm install with adding it to your package.json like so

"scripts": {
  "postinstall": "node postinstall.cjs"
}

Examples

It works in these plain ES6 module based apps and components, which must not be transpiled or compiled to run. They work out of the box without transpiling, without babel.

API

constructor

/**
 * @param projectRoot Your project root, mostly `__dirname`
 * @param props Configuration properties
 */
constructor(projectRoot = __dirname, props = {})

Default props

props = {
    nodeModulesPath: path.resolve(__dirname, '../../'), // path to `node_modules`
    libraryFolder: "lib", // library folder where the module sources are linked/copied to
    mode: "copy" // set to "symlink" to symlink sources instead of copying
}

method add to a package to the library

/**
 * Add the modules of a node package to the library
 * @param packageName Name of the nmp package
 * @param projectSourceRoot The source root inside the package folder
 * @param fileOrFolder The module source folder or file inside the 'projectSourceRoot'
 */
add(packageName, projectSourceRoot = "src", fileOrFolder = packageName)