Daniel Roe

@majtanmarek I believe you should _already_ be able to configure IPX using runtime config. This is purely a documentation update.

interesting. yes, in that case let's fix the issue in ipx (or if it is as simple as sorting modifiers alphabetically we can do that in nuxt/image as a hotfix)

@riddla I investigated and the issue is that the decoding happens _after_ splitting by modifier, which must be either `&` or `,`. (and `,` can cause [issues within srcset](https://github.com/unjs/ipx/issues/57). we...

would you be able to add a regression test case in `ssr.test.ts` to reproduce the bug and make sure it doesn't happen again? 🙏

I don't think this is right either. that interface is populated dynamically via types that nuxt generates, which should certainly include ipx

this is very likely to be a node issue, perhaps. what version of npm do you have?

That indicates it might be related to the new build directory behaviour, which uses `.nuxt` solely for types, and `node_modules/.cache/nuxt/.nuxt` for production builds (if the `.nuxt/` directory exists)

I think the issue here is that you are running the install without any files present, which makes the generated `.nuxt` folder inaccurate (it's missing all the types). Copying the...

This looks to me like `@vitejs/plugin-vue` might be injected twice (and therefore transforming components twice). https://github.com/storybookjs/storybook/blob/0ca0061c3fde053830aa1b5bdc0fce54776e1e13/code/frameworks/vue3-vite/src/preset.ts#L20-L23 That is because Nuxt injects this plugin after `vite:extendConfig` is resolved (to allow users...

I'm opening a new PR as I don't have permission to push to this one: https://github.com/nuxt/image/pull/2005