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

@eik/webpack-plugin

v2.0.6

Published

WebPack plugin for loading import maps from an Eik server and applying the mapping to ECMAScript modules in preparation for upload to the same server.

Downloads

184

Readme

@eik/webpack-plugin

Plugin to rewrite bare imports to URLs as defined in import maps

WebPack Eik plugin to support the use of import maps to map "bare" import specifiers in ES modules.

Installation

npm install @eik/webpack-plugin

Usage

export default {
	experiments: {
		outputModule: true,
	},
	entry: "/src/input.js",
	mode: "production",
	output: {
		environment: {
			module: true,
		},
		filename: "bundle.js",
		path: "/out/",
	},
	module: {
		rules: [
			{
				test: /\.js$/,
				use: {
					loader: "@eik/webpack-plugin",
					options: {
						path: "/path/to/eik-json-folder",
					},
				},
			},
		],
	},
};

Description

This plugin transforms "bare" import specifiers to absolute URL specifiers in ES modules. The module refered to by the "bare" import specifier will be treated as external and its source will not be included in the bundle but refered to by URL.

The plugin will attempt to read import map URLs from eik.json if present.

The path to the location of an eik.json file can be specified with the path option.

export default {
	//...
	module: {
		rules: [
			{
				test: /\.js$/,
				use: {
					loader: "@eik/webpack-plugin",
					options: {
						path: "/path/to/eik-json-folder",
					},
				},
			},
		],
	},
};

The plugin can also be told which URLs to load import maps from directly using the urls option.

export default {
	//...
	module: {
		rules: [
			{
				test: /\.js$/,
				use: {
					loader: "@eik/webpack-plugin",
					options: {
						urls: ["http://myserver/import-map"],
					},
				},
			},
		],
	},
};

Additionally, individual mappings can be specified using the maps option.

export default {
	//...
	module: {
		rules: [
			{
				test: /\.js$/,
				use: {
					loader: "@eik/webpack-plugin",
					options: {
						maps: [
							{
								imports: {
									"lit-element": "https://cdn.eik.dev/lit-element/v2",
								},
							},
						],
					},
				},
			},
		],
	},
};

If several of these options are used, maps takes precedence over urls which takes precedence over values loaded from an eik.json file.

ie. in the following example

export default {
	//...
	module: {
		rules: [
			{
				test: /\.js$/,
				use: {
					loader: "@eik/webpack-plugin",
					options: {
						path: "/path/to/eik-json-folder",
						urls: ["http://myserver/import-map"],
						maps: [
							{
								imports: {
									"lit-element": "https://cdn.eik.dev/lit-element/v2",
								},
							},
						],
					},
				},
			},
		],
	},
};

Any import map URLs in eik.json will be loaded first, then merged with (and overridden if necessary by) the result of fetching from http://myserver/import-map before finally being merged with (and overriden if necessary by) specific mappings defined in maps. (In this case lit-element)

Plugin result

Bundles will have bare imports mapped to absolute URLs.

Ie. Something like this...

import { LitElement, html, css } from "lit-element";

Will be mapped to something like this...

import { LitElement, html, css } from "https://cdn.eik.dev/lit-element/v2";

Options

This plugin takes the following options:

| option | default | type | required | details | | ------ | -------------- | -------- | -------- | --------------------------------------- | | path | cwd/eik.json | string | false | Path to eik.json file. | | urls | [] | array | false | Array of import map URLs to fetch from. | | maps | [] | array | false | Array of import map as objects. |

Note on ESM with WebPack

This plugin will only apply import maps to ESM modules. Due to this its more or less given that the source of your build must be ESM and that your build output is ESM. WebPack does not by default output ESM so this needs to be configured.

You enable ESM output in WebPack as follows (reference):

export default {
	//...
	experiments: {
		outputModule: true,
	},
	output: {
		environment: {
			module: true,
		},
	},
};

License

See license file.