canirequire › ESM-only › @angular/animations
Is @angular/animations ESM-only? Can you require() it?
Angular - animations integration with web-animations
Last verified Sep 9, 2026 against @angular/animations@22.1.5. Markdown · JSON
ESM-only ESM-only since 13.0.0 — last CommonJS version is 12.2.17
@angular/animations dropped its CommonJS build in 13.0.0 (November 2021). The last version with a plain require()-able CommonJS entry is 12.2.17, published Nov 22, 2022; it declares support for Node.js ^12.14.1 || >=14.0.0.
require("@angular/animations") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it. Node.js 18 has no require(esm), and @angular/animations@22.1.5 declares Node.js ^22.22.3 || ^24.15.0 || >=26.0.0, so 18 is outside its supported range anyway.
@angular/animations@22.1.5 declares engines "^22.22.3 || ^24.15.0 || >=26.0.0", so Node.js 18, 20 are outside its supported range regardless of module format.
What to do
- require("@angular/animations") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it.
- From a CommonJS file, use a dynamic import inside an async function: const animations = await import("@angular/animations"). That works on every Node.js version the package supports (^22.22.3 || ^24.15.0 || >=26.0.0).
- If you need a synchronous require() or run Node.js 18: npm install @angular/animations@12.2.17, the last CommonJS release (published Nov 22, 2022); it declares Node.js ^12.14.1 || >=14.0.0.
- @angular/animations@22.1.5 declares engines "^22.22.3 || ^24.15.0 || >=26.0.0", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
- TypeScript: types are bundled; install nothing extra.
- This package is deprecated: @angular/animations is deprecated. Use `animate.enter` and `animate.leave` instead. For more information see: https://v22.angular.dev/guide/animations.
Deprecated: @angular/animations is deprecated. Use `animate.enter` and `animate.leave` instead. For more information see: https://v22.angular.dev/guide/animations.
Does @angular/animations@22.1.5 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@angular/animations") from a CommonJS file and import "@angular/animations" from an ES module.
| Runtime | require("@angular/animations") | import "@angular/animations" |
|---|---|---|
| Node.js 18 | ✗ failsERR_REQUIRE_ESM | ✗ failsError |
| Node.js 20 | ✗ failsError | ✗ failsError |
| Node.js 22 | ✗ failsError | ✗ failsError |
| Node.js 24 | ✗ failsError | ✗ failsError |
| Node.js 26 | ✗ failsError | ✗ failsError |
| Bun 1.4.0 | ✗ failsError | ✗ failsError |
How to import @angular/animations
ES modules (import)
import * as animations from "@angular/animations";Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.
CommonJS (require)
// require("@angular/animations") failed in our probe on Node.js 22.12+ and newer as well (The service 'AnimationBuilder' needs to be compiled using the JIT compiler, but '@angular/compiler' is not available); see the runtime table.
// Any Node.js version the package supports (^22.22.3 || ^24.15.0 || >=26.0.0), from an async function:
async function main() {
const animations = await import("@angular/animations");
}
// Or pin the last CommonJS release (declares Node.js ^12.14.1 || >=14.0.0):
// npm install @angular/animations@12.2.17Module 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 (548 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 20.3.26 – 22.1.5 | ESM-only | Jul 8, 2026 |
Frequently asked
Is @angular/animations ESM-only?
@angular/animations@22.1.5 is ESM-only. @angular/animations dropped its CommonJS build in 13.0.0 (November 2021). The last version with a plain require()-able CommonJS entry is 12.2.17, published Nov 22, 2022; it declares support for Node.js ^12.14.1 || >=14.0.0.
Which version of @angular/animations still supports CommonJS / require()?
12.2.17 is the last version of @angular/animations with a CommonJS build; it declares Node.js ^12.14.1 || >=14.0.0. Install it with "npm install @angular/animations@12.2.17". Every version from 13.0.0 on is ESM-only.
How do I use @angular/animations from a CommonJS file?
From a CommonJS file, use a dynamic import inside an async function: const animations = await import("@angular/animations"). That works on every Node.js version the package supports (^22.22.3 || ^24.15.0 || >=26.0.0). require("@angular/animations") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it. Alternatively pin @angular/animations@12.2.17 (declares Node.js ^12.14.1 || >=14.0.0).
Does @angular/animations work in Bun?
Importing @angular/animations failed in Bun 1.4.0 on Sep 9, 2026: error: The service 'AnimationBuilder' needs to be compiled using the JIT compiler, but '@angular/compiler' is not available.
Does @angular/animations ship TypeScript types?
Yes. @angular/animations bundles its own type declarations; no @types package is needed.
Links
Other esm-only packages
- ansi-styles 7.0.0last CJS
5.2.0 - strip-ansi 7.2.0last CJS
6.0.1 - commander 15.0.0last CJS
14.0.3 - supports-color 11.0.0last CJS
8.1.1 - chalk 6.0.0last CJS
4.1.2 - string-width 8.2.2last CJS
4.2.3 - ansi-regex 6.3.0last CJS
5.0.1 - escape-string-regexp 5.0.0last CJS
4.0.0
Similar popularity
- opn 6.0.0CommonJS
- requirejs 2.3.8CommonJS
- c8 12.0.0CommonJS
- eslint-plugin-flowtype 8.0.3CommonJS
- @angular/platform-browser-dynamic 22.1.5ESM-only
- markdown-it-anchor 10.0.0CommonJS
- popper.js 1.16.1CommonJS
- @babel/cli 8.0.4No entry