-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
Next 6 with Babel 7 beta #4691
Comments
Babel v7 is a must, but it certainly should be up to date, which it is not. Babel is pinned at |
See #4707 |
Well, here's the answer: #4733 |
PSA: Babel 7 entered RC stage, so we should soon be able to see a new canary version with bumped Babel dependencies. Looking forward :D |
Fixes #4691 Fixes #4614 This PR gives path to vercel/next-plugins#242 I did not add or remove `^` near dependency versions in package.json files. However, I don't exclude that some changes can be made given that rc is more stable than beta.
Hi,
This is more a general question than an issue, apologies.
I run next with typescript (I honestly don’t think that this is far fetched or even an exotic combination) and since the dependency bump to Babel 7 beta, some of the typescript features my project depends on don’t work anymore. Some of the Babel language plugins just aren’t there yet and it is confusing.
Don’t take this the wrong way, but why do you guys depend on a beta version (outdated at that) for one of the key components?
I love how you keep the pace up with canary releases et al, but I don’t think Babel 7 is ready yet for prime time, especially in regards to certain TS language features.
The “with-typescript” example works fine, but it’s also super trivial. This shouldn’t be a measurement to determine the level of stability.
By hey, just my five cents. :-)
Oliver
The text was updated successfully, but these errors were encountered: