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]: normalize source path for special app-dir metadata files #11579
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
🦋 Changeset detectedLatest commit: 78e0a7f The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
ztanner
requested review from
TooTallNate,
EndangeredMassa,
trek,
onsclom,
jeffsee55,
erikareads,
timneutkens,
ijjk,
huozhi,
Ethan-Arrowood and
styfle
as code owners
May 10, 2024 19:29
ijjk
previously approved these changes
May 10, 2024
ijjk
approved these changes
May 13, 2024
Merged
EndangeredMassa
pushed a commit
that referenced
this pull request
May 13, 2024
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @vercel/build-utils@8.1.1 ### Patch Changes - [build-utils] pnpm lockfile testing and fixing ([#11591](#11591)) ## vercel@34.1.12 ### Patch Changes - Updated dependencies \[[`67afc2608`](67afc26), [`2f7a6ed5f`](2f7a6ed)]: - @vercel/next@4.2.11 - @vercel/build-utils@8.1.1 - @vercel/node@3.1.2 - @vercel/static-build@2.5.6 ## @vercel/client@13.2.4 ### Patch Changes - Updated dependencies \[[`2f7a6ed5f`](2f7a6ed)]: - @vercel/build-utils@8.1.1 ## @vercel/gatsby-plugin-vercel-builder@2.0.28 ### Patch Changes - Updated dependencies \[[`2f7a6ed5f`](2f7a6ed)]: - @vercel/build-utils@8.1.1 ## @vercel/next@4.2.11 ### Patch Changes - normalize source file locations for special metadata files ([#11579](#11579)) ## @vercel/node@3.1.2 ### Patch Changes - Updated dependencies \[[`2f7a6ed5f`](2f7a6ed)]: - @vercel/build-utils@8.1.1 ## @vercel/static-build@2.5.6 ### Patch Changes - Updated dependencies \[]: - @vercel/gatsby-plugin-vercel-builder@2.0.28 ## @vercel-internals/types@1.0.33 ### Patch Changes - Updated dependencies \[[`2f7a6ed5f`](2f7a6ed)]: - @vercel/build-utils@8.1.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When specifying a functions configuration in
vercel.json
, we attempt to find source files for all entrypoints. This attempts to normalize those source paths for some special cases so that we don't show a build warning for completely normal usage./_not-found
is an entrypoint automatically inserted by Next.js -- if we don't find a source file for it, don't warn, as the user might not have added onefavicon.ico
andopengraph-image.<ext>
will be bundled asfavicon.ico/route.js
but the source file will be the raw extension.