Repository navigation
Eliminate .NET version .js suffix in module import - #263
Merged
Merged
Conversation
Vladimir Morozov (vmoroz)
approved these changes
Apr 8, 2024
This file contains hidden or 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
2 participants
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.
This fixes a small usability issue that has been bugging me while writing docs...
When loading a specific version of .NET using ES
import, the.jssuffix was required after the target framework moniker:While the
.jssuffix is normal for importing ES module files, the versions are not really meant to be modules but alternative entry-points. Anyway this uses theexportsproperty inpackage.jsonto declare those entry-points without a.jssuffix:(Package entry-points can be conditional and work with CommonJS also. I might use them in some other ways in the future.)