canirequire › CommonJS › pnp-webpack-plugin
Is pnp-webpack-plugin ESM-only? Can you require() it?
plug'n'play resolver for Webpack
Last verified Sep 9, 2026 against pnp-webpack-plugin@1.7.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
pnp-webpack-plugin ships CommonJS only. require("pnp-webpack-plugin") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6. import "pnp-webpack-plugin" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
What to do
- require("pnp-webpack-plugin") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.
- From ES modules use the default import: import pnpWebpackPlugin from "pnp-webpack-plugin"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for pnp-webpack-plugin; declare the module yourself if you need them.
Does pnp-webpack-plugin@1.7.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("pnp-webpack-plugin") from a CommonJS file and import "pnp-webpack-plugin" from an ES module.
| Runtime | require("pnp-webpack-plugin") | import "pnp-webpack-plugin" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4.0 | ✓ works | ✓ works |
How to import pnp-webpack-plugin
ES modules (import)
import pnpWebpackPlugin from "pnp-webpack-plugin";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const pnpWebpackPlugin = require("pnp-webpack-plugin");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (19 versions; the newest 19 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 1.7.0 | CommonJS | Sep 13, 2018 |
Frequently asked
Is pnp-webpack-plugin ESM-only?
pnp-webpack-plugin@1.7.0 is a CommonJS package. pnp-webpack-plugin ships CommonJS only. require("pnp-webpack-plugin") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6. import "pnp-webpack-plugin" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import pnp-webpack-plugin with ES module syntax?
Yes. import pnpWebpackPlugin from "pnp-webpack-plugin" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does pnp-webpack-plugin work in Bun?
Yes. import "pnp-webpack-plugin" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does pnp-webpack-plugin ship TypeScript types?
No. pnp-webpack-plugin ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @storybook/addon-interactions 8.6.14Dual
- vue-template-compiler 2.7.16CommonJS
- rollup-plugin-typescript2 0.37.0CommonJS
- @fortawesome/free-solid-svg-icons 7.3.1Dual
- rollup-plugin-dts 6.5.1Dual
- @oclif/config 1.18.17CommonJS
- @sveltejs/kit 2.70.3ESM-only
- sequelize 6.37.8Dual