This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
fix(docs): prefer ESM exports of dependencies when bundling with esbuild #450
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
AlCalzone
changed the title
hawkticehurst
approved these changes
Mar 21, 2023
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.
Link to relevant issue
This pull request resolves #
Description of changes
When following the getting started guide, I got stuck because
esbuildseems to prefer the UMD exports of some transpiled modules. Those can not be statically analyzed and cause runtime errors for missing dependencies - in my casevscode-json-languageserviceand some of its dependencies.By telling
esbuildto prefer themodulefield overmain, this issue gets avoided.