Skip to content

Conversation

@lucacasonato
Copy link
Member

@lucacasonato lucacasonato commented May 20, 2022

This is a pre-requisite for WASM imports that additionally allows us to
minimize clones when doing things like BOM stripping.

Previously, if a specifier was imported more than once, with conflicting
assertions, we'd only really consider the final import. This is wrong:
conflicting assertions are an error in-themselves already. I think this
behaviour is still wrong, because if a module is imported with incorrect
assertions later in the graph after the module has already been loaded by
an import with a correct assertion, no error will be raised.
This is a pre-requisite for WASM imports that additionally allows us to
minimize clones when doing things like BOM stripping.
Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

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

LGTM, but let's open downstream draft PRs before merging.

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.

3 participants