Gathering detailed insights and metrics for @ember-decorators/babel-transforms
Gathering detailed insights and metrics for @ember-decorators/babel-transforms
Gathering detailed insights and metrics for @ember-decorators/babel-transforms
Gathering detailed insights and metrics for @ember-decorators/babel-transforms
npm install @ember-decorators/babel-transforms
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (95.07%)
HTML (2.92%)
TypeScript (1.98%)
CSS (0.02%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
357 Stars
481 Commits
96 Forks
10 Watchers
34 Branches
63 Contributors
Updated on May 31, 2025
Latest Version
5.2.0
Package Id
@ember-decorators/babel-transforms@5.2.0
Size
3.39 kB
NPM Version
lerna/3.10.2/node@v10.15.0+x64 (darwin)
Node Version
10.15.0
Published on
Apr 06, 2019
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
4
25
Enables your app or addon to use decorators for ES6 classes.
1# latest version 2ember install "@ember-decorators/babel-transforms" 3 4# latest 2.x version 5ember install "@ember-decorators/babel-transforms@^2"
If you're developing an addon and only intend to use decorators in your tests and / or dummy app (tests/dummy
), just install this addon as a regular devDependency:
ember install @ember-decorators/babel-transforms
You can now use decorators in your tests/*
directories, but not in your addon
directory.
If you're developing an addon that only uses decorators interally, e.g. you don't export any decorators that the user is supposed to use, then it's sufficient to install this addon with the -S
flag, so it is added as a dependency
as opposed to the default devDependency
ember install -S @ember-decorators/babel-transforms
In addition to tests/*
, you can now use decorators in your addon
directory. However, do not make them public API, i.e. do not expect the user of you addon to be able to use these decorators.
If you want to not only employ decorators internally, but also make them public API, so that users of your addon can use your decorators, then the consuming app or addon has to be properly configured for decorator usage.
This means, that users of your addon are required to add @ember-decorators/babel-transforms
to their project as well. You can either instruct them to do so in your installation instructions and link them here or automatically add the dependency in the default blueprint using addAddonToProject
:
1// blueprints/<your-addon-name>/index.js 2module.exports = { 3 normalizeEntityName() {}, // no-op since we're just adding dependencies 4 5 afterInstall() { 6 return this.addAddonToProject('@ember-decorators/babel-transforms'); // is a promise 7 } 8};
You can also add it as a dependency
(as opposed to the default devDependency
):
1// blueprints/<your-addon-name>/index.js
2module.exports = {
3 normalizeEntityName() {}, // no-op since we're just adding dependencies
4
5 afterInstall() {
6 return this.addAddonToProject({
7 name: '@ember-decorators/babel-transforms',
8 blueprintOptions: { save: true }
9 }); // is a promise
10 }
11};
Also, don't forget to add @ember-decorators/babel-transforms
to your own addon in the first place. :wink:
ember install -S @ember-decorators/babel-transforms
You can configure this addon in you ember-cli-build.js
file:
1/* eslint-env node */ 2'use strict'; 3 4const EmberAddon = require('ember-cli/lib/broccoli/ember-addon'); 5 6module.exports = function(defaults) { 7 const app = new EmberAddon(defaults, { 8 '@ember-decorators/babel-transforms': { 9 disable: false 10 } 11 }); 12 13 return app.toTree(); 14};
The only option is disable
, which defaults to false
. If you set disable
to true
, Babel will not get configured for decorators.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 3/12 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
164 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More