-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
chore: remove regenerator runtime completely #7599
Conversation
const exportedModules = new Map([ | ||
['foo', 'foo'], | ||
['bar', 'bar'], | ||
['regenerator-runtime/runtime', 'fakeRegenerator'], |
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.
fakeRegenerator can be removed now
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.
This was more of a PoC (and I'm too lazy to run the tests on multiple nodes, so opened this up so CI could run), we should close this and go for yours 🙂
@@ -3,9 +3,7 @@ | |||
"version": "0.0.0", | |||
"name": "example-async", | |||
"devDependencies": { | |||
"@babel/plugin-transform-runtime": "*", |
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.
this plugins is still used by the example, probably works because our deps have this plugins somewhere
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 remove it from the babel config, preset-env
should be enough
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.
it then reports that regeneratorRuntime is not defined 🤔
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.
nvm that was because of the target missing
Intermittent node 8 failure, but since both node 6 and node 10 passed I'll call this a success. But let's land #7595 instead 🙂 |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Alternative to #7595
Test plan
Green CI?