Skip to content
PluginStats

@eik/webpack-plugin weekly downloads statistics

By eik · npm · Webpack plugins

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.

View on npm Fresh · Oct 18, 2026

@eik/webpack-plugin has 75 recorded weekly downloads on npm, a decrease of 16.7% over the past 30 days, ranking #1776 of 2,322 tracked listings.

Weekly downloads
75
Official API · Oct 18, 2026
7-day growth
+53.1%
+26 weekly downloads
30-day growth
-16.7%
-15 weekly downloads
90-day growth
+257%
+54 weekly downloads
Rank
#1776
Among tracked npm listings

About @eik/webpack-plugin

@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:

optiondefaulttyperequireddetails
pathcwd/eik.jsonstringfalsePath to eik.json file.
urls[]arrayfalseArray of import map URLs to fetch from.
maps[]arrayfalseArray 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.

Description from the npm listing.

  • webpack-plugin
  • webpack.js
  • webpack
  • import
  • url
  • esm

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

@eik/webpack-plugin weekly downloads on npm, last 90 days: 75 weekly downloads as of Oct 18, 2026, +257% over 90 days.@eik/webpack-pluginWeekly downloads on npm · Last 90 days75downloads / week+257% over 90 days050100150200250300350400Jul 20Aug 4Aug 19Sep 3Sep 18Oct 3Oct 18downloads / weekobservedarchived (Internet Archive)no observationsJul 22, 2026 – Oct 18, 2026 · 89 observations · Updated Oc…pluginstats.com
@eik/webpack-plugin weekly downloads on npm, last 90 days: 75 weekly downloads as of Oct 18, 2026, +257% over 90 days.

7/30/90-day growth

@eik/webpack-plugin weekly downloads growth on npm: +53.1% over 7 days, -16.7% over 30 days, +257% over 90 days.@eik/webpack-pluginWeekly downloads growth on npm75downloads / week now7-day growth+26 weekly downloads+53.1%30-day growth-15 weekly downloads-16.7%90-day growth+54 weekly downloads+257%Growth vs. nearest observation to each baseline date · Updated Oct 18, 2026pluginstats.com
@eik/webpack-plugin weekly downloads growth on npm: +53.1% over 7 days, -16.7% over 30 days, +257% over 90 days.

Ranking history

@eik/webpack-plugin npm ranking history: currently #1776 (by weekly downloads).@eik/webpack-pluginnpm ranking · by weekly downloads · Last 90 days#1776current rank#1700#1710#1720#1730#1740#1750#1760#1770#1780Jul 22Aug 6Aug 21Sep 5Sep 20Oct 5Oct 20rankOct 18, 2026 – Oct 20, 2026 · 3 observations · Updated Oct 18, 2026pluginstats.com
@eik/webpack-plugin npm ranking history: currently #1776 (by weekly downloads).

Listing placement

All npm2,320 listings · 116 pages · 1,162 shown · page 89, #20 (overall #1,780)
All npm: every listing in weekly downloads order

Listing placement

Webpack plugins251 listings · 13 pages · page 6, #17 (overall #117)
Webpack plugins: every listing in weekly downloads order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (122)
Recent weekly downloads observations for @eik/webpack-plugin
Date (UTC)Weekly downloadsChange vs. previous
75+8
67-4
71+22
490
49-3
520
52+3
49+26
23-28
51-5
56-18
74-16
90-18
108—

Similar npm Webpack plugins plugins

All 20 @eik/webpack-plugin alternatives

Data source

Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.

Listing: https://www.npmjs.com/package/@eik/webpack-plugin. First seen Oct 16, 2026; last successful collection Oct 20, 2026. See the methodology.