fix(vite): getting the dist build to work correctly with vite again #6452
+1
−1
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.
Related Issue: #6419
Summary
This fixes an issue with lazy-loading components when using Calcite Components in a Vite project with the
dist
Stencil output target.Here's how I verified this fix locally:
calcite-components-examples
npm install
main.js
with:npm run build
to generate the newdist
build from the updated stencil configuration.npm link
from withincalcite-components
npm link @esri/calcite-components
which will symlink the calcite dependency in npm to resolve file path imports to the locally-installed calcite-components instance instead of the npm-downloaded copy.npm run dev
from within the vite project.