canirequire

canirequire › CommonJS › tsconfig-paths-webpack-plugin

Is tsconfig-paths-webpack-plugin ESM-only? Can you require() it?

Load modules according to tsconfig paths in webpack.

Last verified Sep 9, 2026 against tsconfig-paths-webpack-plugin@4.2.0. JSON

CommonJS CommonJS — require() works on every Node.js version

tsconfig-paths-webpack-plugin ships CommonJS only. require("tsconfig-paths-webpack-plugin") works everywhere. import "tsconfig-paths-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.

Latest
4.2.0 (Nov 15, 2024)
Module format
CommonJS
Last CommonJS version
4.2.0
TypeScript types
Bundled
Node engines
>=10.13.0
Weekly downloads
15.4M
License
MIT

Does tsconfig-paths-webpack-plugin@4.2.0 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("tsconfig-paths-webpack-plugin") from a CommonJS file and import "tsconfig-paths-webpack-plugin" from an ES module.

Runtimerequire("tsconfig-paths-webpack-plugin")import "tsconfig-paths-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✓ works✓ works

How to import tsconfig-paths-webpack-plugin

ES modules (import)

import tsconfigPathsWebpackPlugin from "tsconfig-paths-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 tsconfigPathsWebpackPlugin = require("tsconfig-paths-webpack-plugin");

Module format by version

Derived from the type, main and exports fields of every stable release on npm (33 versions; the newest 33 shown).

VersionsFormatFirst published
0.1.0 – 4.2.0CommonJSJul 10, 2017

Frequently asked

Is tsconfig-paths-webpack-plugin ESM-only?

tsconfig-paths-webpack-plugin@4.2.0 is a CommonJS package. tsconfig-paths-webpack-plugin ships CommonJS only. require("tsconfig-paths-webpack-plugin") works everywhere. import "tsconfig-paths-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 tsconfig-paths-webpack-plugin with ES module syntax?

Yes. import tsconfigPathsWebpackPlugin from "tsconfig-paths-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 tsconfig-paths-webpack-plugin work in Bun?

Yes. import "tsconfig-paths-webpack-plugin" loaded successfully in Bun 1.4 on Sep 9, 2026.

Does tsconfig-paths-webpack-plugin ship TypeScript types?

Yes. tsconfig-paths-webpack-plugin bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity