Rich Harris

@johnnysprinkles let us know if we're ok to close this issue — thanks

The directory is used for more than Vite builds, so we can't use `vite.build.outDir` — Kit needs to control it. Having it be configurable seems reasonable, we would just need...

I did, yeah — closed by accident. An `outDir` outside the project directory _should_ work as long as you don't specify `paths` config, but we need to address that case...

It _does_ seem reasonable to reuse data nodes if there's overlap between the source and target (this isn't specific to parent-child relationships), though we need to be careful that things...

I agree with Dominik that it's probably a slippery slope. I think throwing an error telling the user to change it could be good, it just felt like a lot...

Please include an actual reproduction, as requested in the issue template

This is a dupe of https://github.com/sveltejs/kit/issues/5298#issuecomment-1238288084. Ultimately I don't think matchers are the right solution for internationalising routes, even if they're the best tool we have right now

Huh. Interestingly it works correctly in Firefox, but not in Chrome

SvelteKit was _never_ handling `process.env.NODE_ENV` so I assume this is a change in Vite. I'd prefer that Vite be responsible for this sort of thing, but we need to figure...

Yep, this should work now — we can probably close this issue. Any objections?