Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: inline dynamic imports for ssr-webworker (fixes #9385) #9401

Merged
merged 4 commits into from
Jul 28, 2022

Conversation

sapphi-red
Copy link
Member

@sapphi-red sapphi-red commented Jul 28, 2022

Description

#8641 disabled inlineDynamicImports for ssr-webworker. Instead, it should disable for ssr-node.
This PR fixes that.

fixes #9385

Additional context


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines and follow the Commit Convention.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

@sapphi-red sapphi-red added p4-important Violate documented behavior or significantly improves performance (priority) regression The issue only appears after a new release labels Jul 28, 2022
@sapphi-red sapphi-red marked this pull request as ready for review July 28, 2022 06:45
@sapphi-red
Copy link
Member Author

This PR passed ecosystem-ci: https://github.com/vitejs/vite-ecosystem-ci/actions/runs/2751820829.

) {
return {
code:
`import { __ssr_vue_processAssetPath } from '${virtualId}';` +
`import { __ssr_vue_processAssetPath } from '${virtualId}';__ssr_vue_processAssetPath;` +
Copy link
Member

Choose a reason for hiding this comment

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

Why is this needed? And why the guard against importing it twice has been removed?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure why this is needed. But if I remove this, assets/Home.hash.js won't include the import.

About the guard, it was an artifact during struggling about that. 😅 Thanks for pointing it out!

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe moduleSideEffects: 'no-treeshake' means the module is side-effectful but the imports can be removed if not used?

Copy link
Member

Choose a reason for hiding this comment

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

I would think that should be respected, but we could move with your change for the moment until we find out a better way.

@patak-dev patak-dev merged commit cd69358 into main Jul 28, 2022
@patak-dev patak-dev deleted the fix/inline-dynamic-imports-worker branch July 28, 2022 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p4-important Violate documented behavior or significantly improves performance (priority) regression The issue only appears after a new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SSR web worker build with noExternal: true omit dynamic imports
2 participants