docs: Exclude Beast ORM from optimizeDeps #17
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
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.
In this commit, we exclude the "beast-orm" module from the optimizeDeps configuration in Vite. By doing so, we prevent Vite from optimizing the dependency, providing manual control over the optimization process for Beast ORM.
This exclusion is beneficial in cases where manual optimization is preferred or if there are issues related to the optimization of Beast ORM. Developers should ensure that the dependencies and their versions are compatible and up-to-date.
The configuration uses the defineConfig function to create a Vite configuration object. The optimizeDeps property is utilized to configure dependency optimization, and the "beast-orm" module is specified in the exclude array to indicate its exclusion from the optimization process.
Additionally, the Svelte plugin is included in the configuration through the plugins array. Developers can customize this configuration according to the specific requirements and dependencies of their project.