Conversation
|
|
@nuxt/kit
@nuxt/nitro-server
nuxt
@nuxt/rspack-builder
@nuxt/schema
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
WalkthroughThis pull request modifies the loader configuration in Possibly related PRs
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Tip ✨ Issue Enrichment is now available for GitHub issues!CodeRabbit can now help you manage issues more effectively:
Disable automatic issue enrichmentTo disable automatic issue enrichment, add the following to your issue_enrichment:
auto_enrich:
enabled: falseThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
CodSpeed Performance ReportMerging #33858 will improve performances by 12.17%Comparing Summary
Benchmarks breakdown
Footnotes |
|
I'm not sure about tests but is it possible to have test case for numbered layers directories? |
|
Hey @danielroe Is it possible to change order of layers via Benefits:
I would love to have this feature, Should I raise a feature request for this? |
|
unfortunately that's not possible with local layers. if you want that, move them out of the |
🔗 Linked issue
resolves #33855
🐞 Can't import variables from ordered layers in nuxt config #33855
Nuxt’s auto layer discovery strips the trailing slash from layers/* results.
When a layer folder contains a dot (e.g. 01.base), the resolver interprets it as a file extension instead of a directory and throws:
Cannot find module 'layers/01.base'The change makes Nuxt always keep a trailing slash on auto-detected layer paths, so dotted folders are consistently handled as directories. Fairly simple, straight forward fix.
Cheers!