Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Contributor
Author
|
@alishaz-polymath could you verify whether this implementation supports Windows? 😅 |
zomars
approved these changes
Aug 26, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes an issue with
[...static].jsxthat seems to bundle all images up into one giant serverless function within Vercel.Next 12.2 allows turning off next/image optimisation which I’ve done; optimisation is probably broken across the board on![]()
tags where this became a problem (see logo’s, app icons). We don’t really care about that feature anyway, not that kind of website.
<Image />for public/ assets but we’ve historically replaced withAlso rewrites don’t seem to work on assets, redirect worked no problem but a rewrite just didn’t.