Eliminate .NET version .js suffix in module import #263
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.js
suffix was required after the target framework moniker:While the
.js
suffix is normal for importing ES module files, the versions are not really meant to be modules but alternative entry-points. Anyway this uses theexports
property inpackage.json
to declare those entry-points without a.js
suffix:(Package entry-points can be conditional and work with CommonJS also. I might use them in some other ways in the future.)