canirequire › CommonJS › babel-plugin-transform-decorators-legacy
Is babel-plugin-transform-decorators-legacy ESM-only? Can you require() it?
A plugin for Babel 6 that (mostly) replicates the old decorator behavior from Babel 5.
Last verified Sep 9, 2026 against babel-plugin-transform-decorators-legacy@1.3.5. JSON
CommonJS CommonJS — require() works on every Node.js version
babel-plugin-transform-decorators-legacy ships CommonJS only. require("babel-plugin-transform-decorators-legacy") works everywhere. import "babel-plugin-transform-decorators-legacy" 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.
Does babel-plugin-transform-decorators-legacy@1.3.5 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("babel-plugin-transform-decorators-legacy") from a CommonJS file and import "babel-plugin-transform-decorators-legacy" from an ES module.
| Runtime | require("babel-plugin-transform-decorators-legacy") | import "babel-plugin-transform-decorators-legacy" |
|---|---|---|
| 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 babel-plugin-transform-decorators-legacy
ES modules (import)
import babelPluginTransformDecoratorsLegacy from "babel-plugin-transform-decorators-legacy";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 babelPluginTransformDecoratorsLegacy = require("babel-plugin-transform-decorators-legacy");Module format by version
Derived from the type, main and exports fields of every stable release on npm (10 versions; the newest 10 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 1.3.5 | CommonJS | Dec 2, 2015 |
Frequently asked
Is babel-plugin-transform-decorators-legacy ESM-only?
babel-plugin-transform-decorators-legacy@1.3.5 is a CommonJS package. babel-plugin-transform-decorators-legacy ships CommonJS only. require("babel-plugin-transform-decorators-legacy") works everywhere. import "babel-plugin-transform-decorators-legacy" 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 babel-plugin-transform-decorators-legacy with ES module syntax?
Yes. import babelPluginTransformDecoratorsLegacy from "babel-plugin-transform-decorators-legacy" 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 babel-plugin-transform-decorators-legacy work in Bun?
Yes. import "babel-plugin-transform-decorators-legacy" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does babel-plugin-transform-decorators-legacy ship TypeScript types?
No. babel-plugin-transform-decorators-legacy 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
- rollup-plugin-vue 6.0.0CommonJS
- rollup-plugin-scss 4.0.1CommonJS
- mockjs 1.1.0CommonJS
- download-git-repo 3.0.2CommonJS
- gulp-clean 0.4.0CommonJS
- jscs 3.0.7CommonJS
- rollup-plugin-filesize 10.0.0CommonJS
- gulp-jshint 2.1.0CommonJS