-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
fix(nuxt)!: remove public and assets alias to fix relative imports from other sources #32119
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(nuxt)!: remove public and assets alias to fix relative imports from other sources #32119
Conversation
|
@nuxt/kit
nuxt
@nuxt/schema
@nuxt/rspack-builder
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
Looks like removing the aliases resulted in <img
src="~/assets/logo.svg"
class="h-20 mb-4"
> not working |
CodSpeed Performance ReportMerging #32119 will not alter performanceComparing Summary
|
Reason: vitejs/vite-plugin-vue#15 |
We likely need to add a vite plugin of our own to add support for this until/unless it's fixed upstream. I think there should be no similar issue with the |
Do you mean keeping the |
I mean, there is no problem with getting rid of it |
Warning Rate limit exceeded@danielroe has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 10 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThe changes update the handling of directory aliases within configuration files and their associated tests. Specifically, the aliases for the "assets" and "public" directories have been removed from the common configuration resolver and the corresponding test snapshot. In contrast, new asynchronous resolvers for alias mappings based on the assets directory have been introduced in both the Vite and Webpack configuration schemas. These resolvers dynamically generate alias entries for the assets directory by resolving its path relative to the source directory, and merge any user-defined aliases. No changes were made to exported or public entity declarations. ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
🔗 Linked issue
should fix #26164
📚 Description
Reference
This PR removes the explicit
assets
andpublic
alias. This should fix for example any false positive resolved asset from node modules.