Skip to content

fix(externals): distinguish “module” and “import” in “module-import”#18790

Merged
alexander-akait merged 1 commit intowebpack:mainfrom
fi3ework:fix-module-import
Sep 25, 2024
Merged

fix(externals): distinguish “module” and “import” in “module-import”#18790
alexander-akait merged 1 commit intowebpack:mainfrom
fi3ework:fix-module-import

Conversation

@fi3ework
Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

To reproduce: Given there's an external module 'module-a' both being imported by static-import and dynamic import, and the external type is set to 'module-import'.

Expected: The static import becomes ⁠'module', while the other one is ⁠'import'.

Actual: Both external imports are either 'import' or 'module'.

Why: module identifier does not count in dependencyMeta which is used to distinguish 'module' and 'import' in 'module-import'.

Overview changes:

Did you add tests for your changes?

Yes.

Does this PR introduce a breaking change?

No.

What needs to be documented once your changes are merged?

No.

@webpack-bot
Copy link
Copy Markdown
Contributor

For maintainers only:

  • This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
  • This needs to be backported to webpack 4 (issue will be created when merged)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants