Skip to content
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

Support TC39 Optional Chaining #6

Closed
kesslern opened this issue Dec 11, 2019 · 4 comments
Closed

Support TC39 Optional Chaining #6

kesslern opened this issue Dec 11, 2019 · 4 comments

Comments

@kesslern
Copy link

TC39 added the .? operator for null safe object access. Can this be added to Acorn?

@franktopel
Copy link

franktopel commented Feb 17, 2020

We're also eagerly awaiting this since the day we dropped Babel.

There is already a PR that does this: acornjs/acorn#891

What's preventing this from moving forward?

@adrianheine
Copy link
Member

This is still stuck on estree discussions. I'm also probably not going to implement this separately since there's already an acorn PR.

@guybedford
Copy link

@adrianheine it's unfortunate RollupJS has to be behind other projects here, since eg Babel are involved in those discussions yet are already shipping something. Marjin is traditionally conservative so likely won't push things forward. This means there's a chance all other projects sort of work around this to make something work, leaving RollupJS as the odd one out.

Typically this is exactly the sort of scenario in which being able to use third party plugins allows things to move forward. Especially since Rollup doesn't need to expose the internal parse tree.

Do you think there is anything that can be done on the RollupJS side to help move this forward? There are open collective funds available that could help towards getting something going too if necessary.

@guybedford
Copy link

(when I describe projects working around the issue I'm talking about what happens if the estree block in the worst case does not get ironed out quickly, and projects do their own things / come to their own consensus, which is increasingly seeming the case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants