HMR doesn't work on pages that are added to .nuxtignore file about nuxt

[danielroe]

Are you sure? You should be able to provide a fully custom route with it:

<script setup lang="ts">
definePageMeta({
  path: '/some/:custom'
})
</script>

<template>
  <div>
    Nuxt 3 Playground
  </div>
</template>

<style scoped>

</style>

As far as .nuxtignore is concerned, it's not meant for the purpose you're using it for.

Instead, don't add the pages to .nuxtignore and manually remove them in the pages:extend hook (or modify the page route there).

We might be willing to support custom globs for scanning pages later on.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-zvug7j (Open reproduction)

[danielroe]

This is very much expected. What are you trying to achieve by adding it to a list of ignored files, but adding it to the build manually?

[Sakamitsu]

That's demonstrated in the reproduction. Change the routing of some pages while keeping the original file names. Aliases don't solve this problem. Nuxt also has app/router.options.ts, which perfectly solves this problem. However, I think the behavior of hooks in nuxt.config.ts is not entirely clear from the documentation.

If I can add them manually, why doesn't HMR work?
Why am I able to add these pages in nuxt.config.ts if I have them in .nuxtignore? It seems that the expected behavior would be that Nuxt shouldn't acknowledge their existence at all.

[danielroe]

Have you tried setting the path in definePageMeta?

[Sakamitsu]

I use typed-router module and it doesn't support definePageMeta, see this issue victorgarciaesgi/nuxt-typed-router#81
However, even when I use definePageMeta, it still doesn't resolve the ambiguities mentioned above.