Daniel Roe
Daniel Roe
the issue is the subdependencies coming in from sanity deps. many of them are not valid esm which is why they have to be added to optimizeDeps in vite. unfortunately...
in what environment do they not work? can you give me more info on how to reproduce? the tests work for me locally on macos, as well as in CI...
the purpose of the inline js is to capture errors that occur before vue has hydrated the page we might also be able to add a script in `` that...
IIRC, it was because Vercel allow users to pick a subdirectory, and in this case they look for build output within that subdirectory rather than at workspace root. I wonder...
@tobychidi would you raise an issue at https://github.com/unjs/nitro ?
This is likely caused by this plugin which we use to transform page metadata: https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/pages/plugins/page-meta.ts
Closing as @McSundae is correct here. I hope that was helpful 🙏
my guess here is that nuxt is _correctly_ ignoring storybook files. like tests, they should not be included in the nuxt build or watcher. the storybook module should, if necessary,...
it doesn't sound like a bug in Nuxt to me. it's an implementation detail in the storybook module.
is there a reason why you need to use `public`? shouldn't `NUXT_IPX_ALIAS` work just as well, given that the endpoint is only called on the server side?