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

@ampath-kenya/packmap

v1.2.0-beta.3

Published

Turn a package.json into a browser-ready import map

Downloads

8

Readme

packmap

Turn a package.json into a browser-ready import map

Quickstart

Install the library:

npm install --save-dev packmap

Now add the following to your package.json:

{
  "scripts": {
    "build": "packmap"
  }
}

And run the following:

npm run build

Explanation of packmap

Packmap will create a browser-ready directory and import map from a package.json file and node_modules. To use it, your packages must meet the following standards:

  1. All package.json dependencies must be in-browser dependencies instead of build-time dependencies.
  2. There must be only one version of every package. Semantic versioning rules apply.
  3. Packages may have directories.lib in their package.json to specify which directory should be made available to the browser.

CLI usage

packmap may be run as a CLI. To see the available options, run the following:

npx packmap --help

CLI Examples

# output to build directory
packmap -o build

# specify path to package.json
packmap -p ../my-package/package.json

# specify path to import-map which overrides generated import-map
packmap --override-map ./override-import-map.json

# specify current working directory to base relative urls on.
# In this example, the main package.json will be loaded from subdir, and the
# outputted dist director will also be created inside of subdir.
packmap --cwd ./subdir

Javascript usage

Packmap is a node package that is used as follows:

const packmap = require("packmap");

const options = {
  // required
  outdir: "dist",

  // required
  package: "path/to/package.json",

  // optional
  overrideMap: "path/to/override-map.json",

  // optional - defaults to process.cwd()
  cwd: "./subdir",

  // optional - defaults to not logging any packmap info messages.
  // The log function can be used to pipe the logged output of packmap to
  // whatever you'd like it to (stdout, other file, something else).
  log(message) {
    console.log(message);
  }
};

packmap(options)
  .then(() => {
    console.log("done!");
  })
  .catch(err => {
    console.error(err);
  });