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

@virtualstate/impack

v1.0.0-alpha.14

Published

ESM Tree Importer

Downloads

6

Readme

@virtualstate/impack

ESM Tree Importer

Support

Node.js supported

Usage

The below command will re-write all import & export urls so that they are fully resolved.

npx @virtualstate/impack esnext

This command will take

import { run } from "./path/to";

If ./path/to exists, the import is kept as is

If ./path/to.js exists, the import will be re-written as:

import { run } from "./path/to.js";

If ./path/to/index.js exists, the import will be re-written as:

import { run } from "./path/to/index.js";

Import maps

The below command will output an import map with all files in the folder & dependencies

# 
npx @virtualstate/impack import-map.json esnext

For example giving the import map of:

{
  "imports": {
    "@virtualstate/promise": "./node_modules/@virtualstate/promise/esnext/index.js"
  }
}

Along with re-writing all import urls, you will get the output:

{
  "imports": {
    "@virtualstate/promise": "esnext/@virtualstate/promise/esnext/index.js",
    "esnext/path/to/inner.js": "esnext/path/to/inner.js",
    "esnext/path/to/index.js": "esnext/path/to/index.js"
  }
}

The below command will output an import map with only the dependent files of this entrypoint file

# 
npx @virtualstate/impack import-map.json esnext/tests/index.js

Any dependency urls that are not provided in the initial import map, are not replaced.

Node subpath patterns

If you were to have an import that used a node subpath pattern, starting with #, if a replacement is not found in the provided import map, the closest package.json with a matching pattern will be used.

For example if your package.json

{
  "imports": {
    "#internal/*.js": "./src/internal/*.js"
  }
}

And used the import:

import Users from "#internal/users";
import Storage from "#internal/storage";

You would get the output:

{
  "imports": {
    "src/index.js": "src/index.js",
    "src/internal/users.js": "src/internal/users.js",
    "src/internal/storage.js": "src/internal/storage.js"
  }
}

Cap'n Proto

The below command will output modules ready to use in a capnp file

npx @virtualstate/impack import-map.json esnext --capnp

For Example:

modules = [
  (name = "esnext/@virtualstate/promise/esnext/index.js", esModule = embed "esnext/@virtualstate/promise/esnext/index.js"),
  (name = "esnext/path/to/inner.js", esModule = embed "esnext/path/to/inner.js"),
  (name = "esnext/path/to/index.js", esModule = embed "esnext/path/to/index.js")
]
# Will replace the modules of workers in a capnp template file
npx @virtualstate/impack import-map.json esnext --capnp=workerd-template.capnp

For example the below template:

const test :Workerd.Worker = (
   modules = [],
   compatibilityDate = "2022-09-16",
);

Will output as:

const test :Workerd.Worker = (
   modules = [
      (name = "esnext/@virtualstate/promise/esnext/index.js", esModule = embed "esnext/@virtualstate/promise/esnext/index.js"),
      (name = "esnext/path/to/inner.js", esModule = embed "esnext/path/to/inner.js"),
      (name = "esnext/path/to/index.js", esModule = embed "esnext/path/to/index.js")
   ],
   compatibilityDate = "2022-09-16",
);