Registry / devops / webpack-import-glob-loader

webpack-import-glob-loader

library1.6.3jsnpmunverified

Webpack preloader that expands glob patterns in ES6 import statements (e.g., `import './foo/**/*.js'`) into individual named imports before bundled. Current version 1.6.3, maintained with occasional updates. It works as a Webpack loader, transforming source code at build time. Differentiates from alternatives like `bulk-import` by focusing on Webpack loader integration and supporting side-effect imports (e.g., `import './**/*.scss'`) and Sass `@import` globs. Use it as a preloader or chained loader.

devops

npm install webpack-import-glob-loader

github ↗package ↗

INSTALL

IMPORT

SIG · WEBPACK-IMPORT-GLO

webpack-import-glob-loader

devopsjavascriptv1.6.3

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

Loader (no direct export)

✓ Configure in webpack config: use: 'webpack-import-glob-loader'

✗ import globLoader from 'webpack-import-glob-loader'

This is a Webpack loader, not a JS module. Do not import directly in application code.

Webpack configuration to use the loader as a preloader for .js files, enabling glob imports.

// webpack.config.js module.exports = { module: { rules: [ { test: /\.js$/, use: 'webpack-import-glob-loader' } ] } }; // In your source code: import modules from "./foo/**/*.js"; // Expands to: // import * as module0 from "./foo/1.js"; // var modules = [module0, ...]

Debug

Known issues

gotchaLoader expands imports before other loaders; order matters in rule chains

fix

Ensure this loader runs first (as preloader) or before transpilers like Babel.

affects: >=1.0

gotchaGlob patterns only work for static imports, not dynamic import()

fix

Use only with static import statements; dynamic imports will not be transformed.

affects: >=1.0

deprecatedWebpack 4 compatibility; may need peer dep adjustments

fix

Update to latest version; if using Webpack 5, ensure loader-utils version is compatible (v2+).

affects: <1.6

Errors

Common errors & fixes

Error: Couldn't find loader 'webpack-import-glob-loader'

Loader not installed or incorrectly specified in webpack config.

fix

Run `npm install webpack-import-glob-loader --save-dev` and check the rule's use value.

Module parse failed: Unexpected token (1:0) You may need an appropriate loader

Loader not applied before Babel or other transpilers due to rule order.

fix

Place webpack-import-glob-loader earlier in the rules array or use `enforce: 'pre'`.

Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

Using glob import inside a function or callback instead of top-level import.

fix

Move import statements to top level; glob expansions require static analysis.

Upgrade

Version history

1.6.3latest on npm

Audit

Dependencies

loader-utilsrequired

globrequired

Agent activity

8 hits · last 30 days

node

Resources

githubhttps://github.com/fred104/webpack-import-glob-loader ↗

packagehttps://www.npmjs.com/package/webpack-import-glob-loader ↗