Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Create 05-07.md #115
Merged
Create 05-07.md #115
Conversation
Co-authored-by: Justin Ridgewell <justin@ridgewell.name>
2020/05-07.md
Outdated
| - In chat: some agreement on keeping the `targets` option as an abstraction (from `preset-env`) vs. only allowing browserslist | ||
| - `targets` should be passed on (resolved to browsers) to plugins/presets so they can be used to inform output (maybe this ties into "assumptions/capabilities" -> example: a transform plugin handles async so output it) | ||
|
|
||
| ## Optional Chaining AST |
nicolo-ribaudo
May 8, 2020
Member
@JLHwung Were we talking about changing this in Babel, or discussing for ESTree? We should write it in the notes.
@JLHwung Were we talking about changing this in Babel, or discussing for ESTree? We should write it in the notes.
JLHwung
May 8, 2020
I think whether we will change OptionalMemberExpression depends on which proposal we will back. Since we need more research efforts on building consensus, I don't expect it will change in the near future. But once decision is made, we should state it clearly on the AST changes (renaming/new shape/new properties, etc.)
I think whether we will change OptionalMemberExpression depends on which proposal we will back. Since we need more research efforts on building consensus, I don't expect it will change in the near future. But once decision is made, we should state it clearly on the AST changes (renaming/new shape/new properties, etc.)
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding notes from today's meeting!
Rendered: https://github.com/babel/notes/blob/762cd08a9c4197449ca3b3a6675554aa5816174b/2020/05-07.md