-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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(turbopack): Ignore no-vc-struct lint in trybuild proc macro tests #74110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This stack of pull requests is managed by Graphite. Learn more about stacking. |
kdy1
approved these changes
Dec 19, 2024
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
build cache
Diff detailsDiff for main-HASH.jsDiff too large to display |
Tests Passed |
This was referenced Dec 19, 2024
bgw
force-pushed
the
bgw/ignore-trybuild-tests-in-lint
branch
from
December 20, 2024 01:50
d24c0c6
to
56a4c25
Compare
ijjk
added
create-next-app
Related to our CLI tool for quickly starting a new Next.js application.
tests
Turbopack
Related to Turbopack with Next.js.
type: next
labels
Dec 20, 2024
bgw
changed the base branch from
bgw/resolved-vc-swc-issue-collector
to
canary
December 20, 2024 01:50
Merge activity
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
create-next-app
Related to our CLI tool for quickly starting a new Next.js application.
created-by: Turbopack team
PRs by the Turbopack team.
tests
Turbopack
Related to Turbopack with Next.js.
type: next
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These tests exist to see that the compiler generates errors when doing similar things to what the lint is designed to catch.
I'd rather exempt these in the lint than in the trybuild tests, as once we get rid of support for the
local
opt-out in theturbo_tasks::value
macro, we shouldn't need the lint anymore (it won't be possible to compile code using an unresolvedVc
in aVcValueType
), but we still will need these trybuild tests.Closes PACK-3673