Avoid transpiling class-properties as they are natively supported #449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is incomplete -- current status: babel problem
goal: make babel do less:
tested at: https://github.com/NullVoxPopuli/babel-transpilation-tests
current problem: (all in babel, not ember-cli-babel) decorator plugin assumes class-properties plugin is needed (it's not)
This is not intended to be merged, but serves as something for folks to point their package.jsons at when they want to see if they can disable class-property transpilation across their whole app and addons.
hopefully: class property transformation is not required for decorators .
(it used to be required tho).
There is an assertion / error that's added by the decorators plugin tho.
Upon manual removal in the above demo everything still works fine.
Here is the the test:
input
output
remove lines which define g and h
the goal of this effort is the following:
To do this, a consuming app must have only one ember-cli-babel instance in the whole node_modules graph.
Related issues: