mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
37ed0493e1
Instead of accessing private files from SvelteKit, we use @sveltejs/load-config to load the Svelte config (that package also knows about checking Vite config). The deadlock is avoided by having a module-level Set to see if we're currently recursing or not. This is necessary for SvelteKit 3 since there the config lives exclusively in the vite config, and the previous logic did not handle that. This also uncovered that we're needlessly rebuilding the generated files in sub builds/workers (SvelteKit, at least below 3, starts off secondary builds; and some things are done in workers), which a new file cache now checks. Picked from stable branch PR #3474 Signed-off-by: Simon Holthausen <simon.holthausen@vercel.com> Co-authored-by: Peter Wielander <mittgfu@gmail.com>
180 B
180 B
@workflow/sveltekit
| @workflow/sveltekit |
|---|
| patch |
Load SvelteKit route configuration through @sveltejs/load-config, including projects that configure SvelteKit exclusively in vite.config.