Registry / web-framework / bundle-loader

bundle-loader

library0.5.6jsnpmunverified

Webpack loader that wraps modules in a require.ensure block to create separate chunks for lazy loading. Version 0.5.6 is the current stable release; last updated February 2018. Key differentiator: simple callback-based API for loading code-split bundles on demand, with options for lazy loading and custom chunk naming. Unlike dynamic import(), it uses webpack's legacy require.ensure and is best suited for webpack 1–3 projects. No longer actively maintained; users should migrate to webpack's built-in dynamic import or @loadable-component.

web-framework

npm install bundle-loader

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · BUNDLE-LOADER

bundle-loader

web-frameworkjavascriptv0.5.6

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.

bundle-loader

✓ import bundle from './file.bundle.js';

✗ const bundle = require('bundle-loader!./file.bundle.js');

bundle-loader returns a function that takes a callback; the callback receives the module exports. Inline loader syntax is deprecated.

bundle-loader (CommonJS)

✓ const bundle = require('./file.bundle.js');

✗ const bundle = require('bundle-loader!./file.bundle.js');

CommonJS require returns the same callback-wrapped function as ESM import. Avoid inline loader syntax.

Options with webpack config

✓ module.exports = { module: { rules: [ { test: /\.bundle\.js$/, use: { loader: 'bundle-loader', options: { lazy: true } } } ] } };

✗ module.exports = { module: { loaders: [ { test: /\.bundle\.js$/, loader: 'bundle-loader?lazy=true' } ] } };

Use module.rules (webpack 2+) and options object instead of inline query strings and loaders array.

Shows how to set up bundle-loader in webpack config and use it to lazy load a module only on user click.

// webpack.config.js module.exports = { entry: './App.js', output: { path: __dirname + '/dist', filename: '[name].js', chunkFilename: '[name].[id].js' }, module: { rules: [ { test: /\.bundle\.js$/, use: { loader: 'bundle-loader', options: { lazy: true, name: '[name]' } } } ] } }; // App.js import loadLazyModule from './lazy.bundle.js'; // The module is not loaded until the callback is invoked document.getElementById('button').addEventListener('click', () => { loadLazyModule((module) => { console.log('Lazy module loaded:', module); }); });

Debug

Known issues

deprecatedbundle-loader uses legacy require.ensure which is discouraged in webpack 4+. Use dynamic import() instead.

fix

Replace bundle-loader usage with dynamic import() and webpack's magic comments.

affects: >=0.5.6

gotchaChunks generated by bundle-loader respect output.chunkFilename, not output.filename. Default chunkFilename may produce unexpected filenames.

fix

Set output.chunkFilename in webpack config (e.g., '[name].[id].js') and use the name option to control chunk naming.

affects: >=0.5.0

gotchaWhen using the name option, [name] refers to the custom name set in options, not the original module name. [hash] does not work correctly in the name option.

fix

Use [name] in the name option to set a custom name; add hash via output.chunkFilename instead.

affects: >=0.5.0

breakingIn webpack 2+, the loader configuration must use module.rules instead of module.loaders. Using loaders will break silently.

fix

Use module.rules array with use/loader property.

affects: >=0.5.4

deprecatedThe package is no longer actively maintained. Last release was in 2018. No new features or bug fixes are expected.

fix

Consider migrating to dynamic import() or a modern code-splitting library like @loadable/component.

affects: >=0.5.6

Errors

Common errors & fixes

require.ensure is not a function

bundle-loader is used with webpack 4+ which removed require.ensure or the loader is not applied correctly.

fix

Ensure the loader is applied to the correct file pattern and consider upgrading to dynamic import(). For webpack 4, use output.enabledChunkLoadingTypes or migrate.

Module not found: Error: Can't resolve 'bundle-loader'

bundle-loader is not installed or webpack configuration is missing resolveLoader.

fix

Run 'npm install bundle-loader --save-dev' and ensure webpack is configured to resolve node_modules loaders.

Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by instanceof Entrypoint instead

Using bundle-loader with webpack 5 which deprecated the entrypoints API.

fix

Use webpack 4 or migrate to dynamic import(). This is a compatibility issue.

Upgrade

Version history

0.5.6latest on npm

Audit

Dependencies

loader-utilsrequiredUsed for parsing loader options and interpolating names

Agent activity

9 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/webpack-contrib/bundle-loader ↗

packagehttps://www.npmjs.com/package/bundle-loader ↗

homepagehttps://webpack.js.org/loaders/bundle-loader ↗