This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
fix: exclude capi from pre-bundling #85
Closed
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
✅ Deploy Preview for capi-multisig ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
statictype
changed the title
|
fixed in #86 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #77
Vite is doing something called pre-bundling during development because it serves ESM modules to the browser and some dependencies need to be transformed
From the docs: If the dependency is small and is already valid ESM, you can exclude it and let the browser load it directly.
Excluding Capi from this optimization results in the dev server starting properly, only that there is a runtime error now: