-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replaced legacy babel-* & shorthand package name usage with @babel/* in README.md's #6820
Conversation
hulkish
commented
Nov 13, 2017
•
edited
Loading
edited
Q | A |
---|---|
Fixed Issues? | N/A |
Patch: Bug Fix? | N/A |
Major: Breaking Change? | N/A |
Minor: New Feature? | N/A |
Tests Added + Pass? | No + Yes |
Documentation PR | Yes |
Any Dependency Changes? | No |
License | MIT |
9d70f3d
to
d5d9dfd
Compare
@@ -20,7 +20,7 @@ And add them in this structure: | |||
|
|||
```js | |||
// es2016 | |||
"@babel/transform-exponentiation-operator": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually this whole document is kind of out of date
babel/experimental/babel-preset-env/data/plugin-features.js
Lines 117 to 123 in 84fe8e4
const es2016 = { | |
"transform-exponentiation-operator": { | |
features: [ | |
"exponentiation (**) operator", | |
], | |
} | |
}; |
referencing the old way to do things + wrong links
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the shorthand format still valid to use? Or is it, or will it be, deprecated/removed in v7? |
@g0t4 it's still valid for v7, just normalizing our docs to not use it since it's confused many people |
@@ -235,15 +235,15 @@ An array of plugins to always include. | |||
|
|||
Valid options include any: | |||
|
|||
- [Babel plugins](https://github.com/babel/babel-preset-env/blob/master/data/plugin-features.js) - both with (`@babel/plugin-transform-spread`) and without prefix (`transform-spread`) are supported. | |||
- [Babel plugins](https://github.com/babel/babel-preset-env/blob/master/data/plugin-features.js) - both with (`@babel/plugin-transform-spread`) and without prefix (`@babel/plugin-transform-spread`) are supported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @hzoo pointed out earlier, the include/exclude options in preset-env
still need to get updated (kinda think we should do this in a separate PR? ¯\(ツ)/¯)
Relevant files:
index.js#L188
available-plugins.js
plugin-features.js
Also, the second shouldn't have a prefix as it's describing that shorthand is supported when declaring include/excludes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be #6825
… plugins from README.md's
@existentialism @g0t4 @hzoo alright how's that, guys? |
|
||
All the Babel plugins (and other packages) that have a `/test/fixtures` are written in a similar way. | ||
|
||
For example, in [`babel-plugin-transform-exponentiation-operator/test`](https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-exponentiation-operator/test): | ||
For example, in [`@babel/plugin-transform-exponentiation-operator/test`](https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-exponentiation-operator/test): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure where to change these because the folder names are still using -
but I guess this is fine.
thanks @hulkish ! |
…plugins from README.md's (babel#6820)