Update: Suppress warnings in production build #241
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
When building for production, various warnings are output which slows down production build. The following changes were made: - Suppress unused export properties (unused-export-let). - Suppress conflicting Svelte resolve warnings (conflicting-svelte-resolve). - Suppress empty chunk warnings (empty-chunk). - Suppress unused module imports (module-unused-import). - Keep other important warnings visible, so we’re still aware of potential issues. Now, production build should be cleaner and faster! 🚀
rajnandan1
approved these changes
Feb 5, 2025
|
Thanks for the contribution ❤️ |
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 building for production, various warnings are output which slows down production build. We don't really need these as warnings should more-so be output (& handled) during development and/or with specific NPM test script. This PR should lower CI/CD build times.
The following changes were made:
We can now specify an (optional)
VITE_BUILD_ENV=productionduringnpm run buildso that these warnings are ‘ignored’. (VITE_BUILD_ENV=development, by default)Now, production build should be cleaner and faster! 🚀