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(vite): let rollup know that public assets are handled as externals #26551

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

danielroe
Copy link
Member

πŸ”— Linked issue

resolves #26379

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

This suppresses the warning vite was throwing when using public assets in CSS, by letting rollup know that these assets can be resolved as externals.

We could also consider simply suppressing logs about these particular assets, if you're worried about any negative performance costs.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have added tests (if possible).
  • I have updated the documentation accordingly.

Copy link

stackblitz bot commented Mar 29, 2024

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

@pi0
Copy link
Member

pi0 commented Mar 29, 2024

Seems something we might expose and reuse from nitro in future for scanning public assets

@danielroe danielroe marked this pull request as draft March 29, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants