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: display manualChunks warning only when a function is not used (#13797) #13798

Merged
merged 2 commits into from Jul 21, 2023

Conversation

jafin
Copy link
Contributor

@jafin jafin commented Jul 12, 2023

Description

Fixes Error logged to console when using manualChunkSplitting and function is used (fix #13797)

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 PR Title 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.

@stackblitz
Copy link

stackblitz bot commented Jul 12, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@jafin jafin changed the title fix: Only display manualChunks warning when a function is not used (#13797) fix: display manualChunks warning only when a function is not used (#13797) Jul 12, 2023
// else, leave the object form of manualChunks untouched, as
// we can't safely replicate rollup handling.
// eslint-disable-next-line no-console
console.warn(
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unrelated to root change, just flagging, is there some global logger to log warnings vs using console.warn?

Copy link
Member

Choose a reason for hiding this comment

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

Good catch. Yes there is a logger but it's only available in configResolved: resolvedConfig.logger.warn(...). I guess we can use a variable to track this and log it out in the configResolved hook instead.

@zorn-v
Copy link

zorn-v commented Jul 13, 2023

There is also typo in message.
Option is build.rollupOptions.output.manualChunks, but not build.rollupOptions.manualChunks

- changed to correct location build.rollupOptions.output.manualChunks
@jafin
Copy link
Contributor Author

jafin commented Jul 13, 2023

There is also typo in message. Option is build.rollupOptions.output.manualChunks, but not build.rollupOptions.manualChunks

Updated with change.

Copy link
Member

@bluwy bluwy left a comment

Choose a reason for hiding this comment

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

Merging this for now.

@bluwy bluwy merged commit 51c271f into vitejs:main Jul 21, 2023
14 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.

Error logged to console when using manualChunkSplitting and function is used.
3 participants