-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Follow-up work for compiling node_modules #3777
Comments
A couple of considerations/questions:
|
Yes please.
Yes.
Yep.
I think it's okay to just verify this manually. I don't expect this to break once we make sure it works. |
I don't think these are relevant? |
Follow-up for #3776.
First thought: we should have an end-to-end test that depends on ES6 package (e.g.
chalk@2.x
). After the build, we can run ESLint in ES5 mode with no rules on the compiled bundle so that end-to-end test fails if we accidentally include ES6 code.There may be more things we need to test. I’m not sure. Thoughts?
My original todos:
engines
field that implies we don't need compilation)sourceType
[8.x] Gain consensus on path forward for "sourceType" for parsing modules vs scripts babel/babel#6242.babelrc
in packages gets ignoredThe text was updated successfully, but these errors were encountered: