loader-runner
npmv4.3.2Runs (webpack) loaders
Safe to adopt
Yes — loader-runner scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 138 days ago. 2 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 138 days ago. 2 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 21 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 7 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding loader-runner to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=6.11.5
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the loader-runner README.
import { runLoaders } from "loader-runner";
runLoaders(
{
resource: "/abs/path/to/file.txt?query",
// String: Absolute path to the resource (optionally including query string)
loaders: ["/abs/path/to/loader.js?query"],
// String[]: Absolute paths to the loaders (optionally including query string)
// {loader, options}[]: Absolute paths to the loaders with options object
context: { minimize: true },
// Additional loader context which is used as base context
loader-runner vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| loader-runnerthis page | 0 | 1 | MIT | 4 months ago |
| rolldown | 81.9M | 8 | MIT | 1 day ago |
| get-nonce | 58.4M | 1 | MIT | 1 day ago |
| minimizer-webpack-plugin | 0 | 1 | MIT | 7 days ago |
| schema-utils | 0 | 2 | MIT | 1 day ago |
| rechoir | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by loader-runner v4.3.2. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (17)
Used by
Popular packages that depend on loader-runner.
Relationship graph
Dependencies (left) and dependents (right) of loader-runner.
Frequently installed together
ECMAScript parser
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
React is a JavaScript library for building user interfaces.
TypeScript definitions for estree
Lodash modular utilities.
React package for working with the DOM.
An AST-based pattern checker for JavaScript.
Prettier is an opinionated code formatter
Node's event emitter for all engines.
Delightful JavaScript Testing.
Support for `import <defer|source>` phase syntax in Acorn
A library to create a trace of your node app per Google's Trace Event format.
Release history
2 releases in the last two years, typically about 133 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 4.3.2latest | 4 months ago | 21 KB | MIT |
| 4.3.1 | 11 months ago | 20 KB | MIT |
| 4.3.0 | 4 years ago | 18 KB | MIT |
| 4.2.0 | 5 years ago | 18 KB | MIT |
| 4.1.0 | 6 years ago | 17 KB | MIT |
| 4.0.0 | 6 years ago | 17 KB | MIT |
| 3.1.0 | 6 years ago | 16 KB | MIT |
| 2.4.0 | 7 years ago | 16 KB | MIT |
| 3.0.0 | 7 years ago | 16 KB | MIT |
| 2.3.1 | 8 years ago | 16 KB | MIT |
| 2.3.0 | 9 years ago | — | MIT |
| 2.2.0 | 10 years ago | — | MIT |
| 2.1.1 | 10 years ago | — | MIT |
| 2.1.0 | 10 years ago | — | MIT |
| 2.0.1 | 10 years ago | — | MIT |
Overview
loader-runner is an npm package that runs (webpack) loaders. It has 1 known dependents in the graph. The latest version is 4.3.2, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need runs (webpack) loaders and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- Large dependency tree (17 direct dependencies) increases install size and audit surface.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Funding
Frequently asked questions
Should I use loader-runner?
Yes — loader-runner scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 138 days ago. 2 releases in the last 2 years.
How do I install loader-runner?
Run `npm install loader-runner` to add loader-runner to your npm project.
What license is loader-runner released under?
loader-runner is distributed under the MIT license.
How popular is loader-runner?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on loader-runner.
Is loader-runner still maintained?
The most recent release of loader-runner (v4.3.2) was published 4 months ago.
Does loader-runner run install scripts?
No. loader-runner does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.