-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
add FixedStaticAsset and TextContentSourceAsset #4692
Merged
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
✅ This change can build |
🟢 CI successful 🟢Thanks |
alexkirsz
approved these changes
Apr 25, 2023
ForsakenHarmony
approved these changes
Apr 25, 2023
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 27, 2023
### What? * support local static metadata files; opengraph-image, twitter-image, favicon, manifest, icon, apple-icon * support global static metadata files: robots.txt, sitemap.xml, favicon.ico * dynamic metadata is not yet implemented, but yields a warning It's implemented a bit different compared to the webpack version. All images will use the usual image machinery, so they are emitted to output directory, content hashed and the url is shared with the same import import in the app. ### Why? Unsupported, and we want to have that. ### How? see also vercel/turborepo#4692 fixes WEB-524
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
### Description needed for metadata support in next.js (#48823)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
### Description needed for metadata support in next.js (#48823)
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
### Description needed for metadata support in next.js (#48823)
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.
Description
needed for metadata support in next.js (vercel/next.js#48823)