build: remove unused vite manifest for consistent build reproducibility #1670
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
1 task
|
For the record, ViteJS has now fixed the order in the manifest.json (vitejs/vite#11540) |
peterpeterparker
added a commit
that referenced
this pull request
Jan 16, 2023
# Motivation In #1666 we have moved scoped styles to global style to workaround the build reproducibility of SvelteKit+ViteJS [#8291](sveltejs/kit#8291). This PR redo the changes has #1670 will solve the reproducibility issue by removing the unused vite manifest file from our build results. # PRs - [x] #1670 # Changes - redo scoped style and remove related global style
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.
Motivation
No
vite-manifest.json, no build reproducibility issue 馃槈.See commented code for details.
Changes
vite-manifest.jsonwith a post build scriptmake-reproducibleas it becomes unusedNotes
I opened today two issues in SvelteKit repo to share what we discovered: