fix(nuxt): support custom route name meta with typedPages

[ChronicStone]

🔗 Linked issue

#21637

❓ 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

Resolves #21637 by parsing at build-time definePageMeta on routes & extracting custom route name

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[ChronicStone]

Following @danielroe feedback, the route name resolver now uses estree parser to extract value from AST. Performance cost seem to be slightly higher on the tests I've made so far, I need to test with a bigger amount of pages to measure more precisely

[ChronicStone]

Updated with your latest advice @danielroe. Now AST parsing happens only if definePageMeta is defined, and happen only on the definePageMeta portion of code to minimize AST parsing.

[danielroe]

Would you mind taking a look at the failing CI?

[ChronicStone]

@danielroe Yep, I planned to have a look tomorrow

[ChronicStone]

Failing CI issue should be solved, unit tests now work properly with new implementation of generateRoutesFromFiles.

Also new unit test implemented to cover route name override

[ChronicStone]

@danielroe Sorry to mention, I know it isn't ideal, but the new error on CI seems to be related to commits from main being merged to local branch.

Considering the mature of the issue, I'm a bit confused on how I sould proceed to fix this.

packages/schema/src/types/config.ts:141: error TS2339: Property 'nitro' does not exist on type 'NitroRuntimeConfig'.

[danielroe]

The CI error is because you haven't added all the dependencies you're using to the package.json dependencies, and they are being inlined in the package output.