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
Acorn 7.3.0 upgrade #3628
Acorn 7.3.0 upgrade #3628
Conversation
Because the build is performed based on the previous build I've left in the fork, perhaps a way to do this will be to remove the fork in a subsequent PR once this is merged? |
8db08c0
to
5e3ddfd
Compare
Thank you for your contribution! ❤️You can try out this pull request locally by installing Rollup via
or load it into the REPL: |
Codecov Report
@@ Coverage Diff @@
## master #3628 +/- ##
=======================================
Coverage 96.54% 96.54%
=======================================
Files 182 182
Lines 6243 6243
Branches 1832 1832
=======================================
Hits 6027 6027
Misses 107 107
Partials 109 109
Continue to review full report at Codecov.
|
7.3.1 was released a bit later today |
I've also added a commit here to upgrade the plugins, as there was a fix in the private class elements package to work with optional chaining here - acornjs/acorn-private-class-elements@c9857bb. I also removed the import meta plugin since that is in Acorn core since acornjs/acorn#943. |
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.
Thanks!
Because the build is performed based on the previous build I've left in the fork
It is not, there was an alias in the Rollup config which replaced acorn by the fork. Which is why your branch was still running the fork. Fixing this revealed that we also needed the new ChainExpression
to prevent Rollup from deoptimizing entirely, which I added.
I also removed the import meta plugin since that is in Acorn core
👍
Acorn just released 7.3.0 with optional chaining support so this PR switches back from the fork we were using to provide this.
I did check that the final ESTree changes don't affect any of the internal code here and as far as I can tell there aren't any issues with this currently, but let me know if I've missed anything.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Description