-
Notifications
You must be signed in to change notification settings - Fork 2.1k
chore: remove turbopack crates #8906
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/@types/loader-runner@2.2.4, npm/@types/node@18.11.18, npm/@types/node@18.13.0, npm/@vercel/ncc@0.34.0, npm/expect@29.5.0, npm/jest-circus@29.5.0, npm/loader-runner@4.3.0, npm/next@14.2.5, npm/node-fetch@2.6.9, npm/npm-run-all@4.1.5, npm/react-dom@18.3.1, npm/react-test-renderer@18.2.0, npm/react@18.2.0, npm/react@18.3.1, npm/semver@7.3.8, npm/webpack@5.93.0 |
3b18821 to
c371b24
Compare
|
These crates got merged into next.js with vercel/next.js#68127 |
with turbopack being removed in #8906, we can also remove mentions of turbopack crates in the prettierignore
with turbopack being removed in #8906, we can also remove this from the vscode settings
with turbopack being removed in #8906, we can also remove these gitattributes files
### Description Left over from #8906
Why?
vercel.com/blog/turbopack-moving-homes