Skip to content

Conversation

@ricochet
Copy link
Contributor

Support semver compatibility when resolving import map entries.
If no exact or wildcard match is found, fall back to matching
map entries on the same semver compatibility track, preferring
the highest compatible version.

Copy link
Collaborator

@vados-cosmonic vados-cosmonic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for landing this @ricochet !

Code looks good to me, would you mind adding an E2E test that makes sure this does what it's supposed to from the user point of view?

packages/jco/test/cli.js is not a bad spot I think

@vados-cosmonic vados-cosmonic force-pushed the feat/semver-map branch 2 times, most recently from 605a536 to 6ee8664 Compare February 11, 2026 15:21
ricochet and others added 3 commits February 12, 2026 00:21
Support semver compatibility when resolving import map entries.
If no exact or wildcard match is found, fall back to matching
map entries on the same semver compatibility track, preferring
the highest compatible version.
@vados-cosmonic vados-cosmonic added this pull request to the merge queue Feb 11, 2026
Merged via the queue into bytecodealliance:main with commit 139e484 Feb 11, 2026
67 of 69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants