ember-modules-codemod 0.1.4
This codemod uses [`jscodeshift`](https://github.com/facebook/jscodeshift) to update an Ember application to use the JavaScript (ES6) module syntax. It can update apps that use the global `Ember`, and will eventually also support apps using [ember-cli-shi
ember-modules-codemod@0.1.4 was published on 2016-11-06. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All ember-modules-codemod versions · Permanent reference to 0.1.4 · View npm registry JSON · Latest release
Package specifications
| Version | 0.1.4 |
|---|---|
| License declaration | MIT |
| Published | 2016-11-06T00:28:22.053Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install ember-modules-codemod 0.1.4
npm install ember-modules-codemod@0.1.4 pnpm add ember-modules-codemod@0.1.4 yarn add ember-modules-codemod@0.1.4
Runtime dependencies
- glob ^7.1.1
- jscodeshift ^0.3.29
Peer requirements
- None declared
Optional dependencies
- None declared
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T22:26:55.614Z