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

@jsenv/import-map

v6.13.3

Published

Helpers to implement importmaps.

Downloads

540

Readme

import-map

Helpers to implement importmaps.

github package npm package github ci codecov coverage

Table of contents

Presentation

@jsenv/import-map can be used to implement the behaviour of importmap as described in the WICG specification. It is written using ES modules and compatible with browsers and Node.js. Amongst other things, this repository is used to provide importmap in ESLint.

Installation

npm install @jsenv/import-map

composeTwoImportMaps

composeTwoImportMaps takes two importMap and return a single importMap being the composition of the two.

import { composeTwoImportMaps } from "@jsenv/import-map"

const importMap = composeTwoImportMaps(
  {
    imports: {
      foo: "bar",
    },
  },
  {
    imports: {
      foo: "whatever",
    },
  },
)

console.log(JSON.stringify(importMap, null, "  "))
{
  "imports": {
    "foo": "whatever"
  }
}

— source code at src/composeTwoImportMaps.js.

normalizeImportMap

normalizeImportMap returns an importMap resolved against an url and sorted.

import { normalizeImportMap } from "@jsenv/import-map"

const importMap = normalizeImportMap(
  {
    imports: {
      foo: "./bar",
      "./ding.js": "./dong.js"
    },
  },
  "http://your-domain.com",
)

console.log(JSON.stringify(importMap, null, '  ')
{
  "imports": {
    "foo": "http://your-domain.com/bar",
    "http://your-domain.com/ding.js": "http://your-domain.com/dong.js"
  }
}

— source code at src/normalizeImportMap.js.

resolveImport

resolveImport returns an import url applying an importMap to specifier and importer. The provided importMap must be resolved and sorted to work as expected. You can use normalizeImportMap to do that.

import { resolveImport } from "@jsenv/import-map"

const importUrl = resolveImport({
  specifier: "../index.js",
  importer: "http://domain.com/folder/file.js",
  importMap: {
    imports: {
      "http://domain.com/index.js": "http://domain.com/main.js",
    },
  },
})

console.log(importUrl)
http://domain.com/main.js

— source code at src/resolveImport.js.

moveImportMap

moveImportMap receives importMap, fromUrl, toUrl and return an importmap where all relative urls and specifiers becomes relative to toUrl instead of fromUrl.

This function exists in case you need to move an importmap file somewhere else in the filesystem. This is not a common use case but might happen.

import { moveImportMap } from "@jsenv/import-map"

const importMapMoved = moveImportMap(
  {
    imports: {
      foo: "./foo.js",
    },
  },
  "file:///project/project.importmap",
  "file:///project/dir/project.importmap",
)
console.log(JSON.stringify(importMap, null, '  ')
{
  "imports": {
    "foo": "../foo.js",
  }
}

— source code at src/moveImportMap.js.