-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
feature(turborepo): fancy package.json errors #8299
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @NicholasLYang and the rest of your teammates on |
🟢 CI successful 🟢Thanks |
🟢 Turbopack Benchmark CI successful 🟢Thanks |
5e41591
to
b0c8574
Compare
c0fd54d
to
2b3d13f
Compare
5e25077
to
792c898
Compare
2b3d13f
to
009574a
Compare
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.
much improved! this raised the question of how we want to handle nested package.json errors (i.e. not from the root package.json) which don't take the path of getting these nice errors, but sounds like we'll follow up with that in the future.
c4a93a8
to
b48e318
Compare
7810bbe
to
653b34e
Compare
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
## Why? - Better package.json errors via [#8299](vercel/turbo#8299), [#8753](vercel/turbo#8753) - Successful [build-and-deploy](https://github.com/vercel/next.js/actions/runs/10127839598) run
Description
More fancy errors! Since we now have span info for package.json files, we can produce errors pointing to locations in package.json.
Testing Instructions