However, when visiting one of these routes in the browser (https://mono.domains/extensions/.autos) after deployment it initally returns a blank page with a 404 status code. Only when the page hydrates on the client side does it actually show the contents.
It should be noted that it does not return the actual 404 page (https://mono.domains/invalidpage), showing that the file actualy exists but the route is not being generated.
I’ve ran some experiments locally and can’t seem to reproduce this behaviour, which is leading me to believe it’s not a Nuxt issue. I’ve also checked smaller Nuxt sites that I have hosted on Netlify and they don’t appear to have this issue, which is leading me to believe it’s due to the large number of routes.
The Netlify ID of the site is glowing-biscochitos-9a1f05.
The confusing part is that it already does this, so I’m unsure why those files aren’t being deployed. When running npm run generate locally it generates 2,060 folders as described in the deploy log snippet in the OP.
The fact that they’re also showing up in the deployment log leads me to believe they’re being generated when the site is deployed too, just then not actually deployed to the server?
One theory could be because we ignore folders with the . in the start of its name. I only thought it’s for folders in the root of the publish folder, but looking at your situation, we might be excluding all dot-files and folders.
The solution would be to remove the dot from the start of each.