Prerender in subprocess

[benmccann]

Describe the problem

SvelteKit exits:

kit/packages/kit/src/vite/index.js

Line 312 in cfd38d4

process.exit(0);

This means you can't have another plugin after the SvelteKit plugin

Describe the proposed solution

Add a new close hook

Have prerender call server.close()

Alternatives considered

No response

Importance

Prevents https://github.com/userquin/pwa-sveltekit-vite from working

Additional Information

No response

[Rich-Harris]

Adding a new hook just for this purpose would be unfortunate, I think — especially since (as far as the user is concerned) the connection between prerendering and close is unclear. We'd also be relying on people to implement close correctly, otherwise their builds would never complete (and people would assume it was because of a SvelteKit bug).

Instead, if we want to avoid exiting the main process, we should probably just do the prerendering in a child process that we can safely kill once prerendering is complete.

[furudean]

A proper exit can't be guaranteed in all environments, especially serverless ones.

[Conduitry]

A proper exit can't be guaranteed in all environments, especially serverless ones.

This issue is just referring to things that would happen during prerendering right, and not at runtime? I would certainly hope that we can rely on all the Node stuff we want while the app is being built, regardless of which platform it is being deployed to.

[furudean]

Ack, my bad.

[userquin]

how about just adding a global end build hook, just call it with some context (Vite and/or SvelteKit) before process.exit is called when an adapter is configured (should also be called when the adapter is not configured)? This way you don't need to change anything, just adding the global end hook call before the exit and also when the adapter is not configured.

IIRC I sent a PR for it a few months ago when trying to include pwa plugin in SvelteKit using the rollup interplugin communication api.

[matiasfha]

Maybe completely wrong my questions here but, that this means that is not possible to run a plugin after the closeBundle hook.
I'm looking for a way to run some transformation on the pre-rendered output files.

Based on what I tried I cannot use writeBundle since the pre-rendered files are not yet there and either closeBundle

Meaning that based on this

async closeBundle() {
			if (svelte_config.kit.adapter) {
				const { adapt } = await import('./build/adapt/index.js');
				await adapt(svelte_config, build_data, prerendered, { log });
			} else {
				console.log(colors.bold().yellow('\nNo adapter specified'));
				// prettier-ignore
				console.log(
					`See ${colors.bold().cyan('https://kit.svelte.dev/docs/adapters')} to learn how to configure your app to run on the platform of your choosing`
				);
			}

			if (is_build && svelte_config.kit.prerender.enabled) {
				// this is necessary to close any open db connections, etc.
				// TODO: prerender in a subprocess so we can exit in isolation
				// https://github.com/sveltejs/kit/issues/5306
				process.exit(0);
			}
		},

The only way to run some transformation on those files is to write a custom adapter right?

[benmccann]

@matiasfha the prerendered output files get generated in writeBundle, so I would expect you to be able to use writeBundle if your plugin is after the SvelteKit plugin. You may have to wait for #5439 to be released first though to ensure that your changes would get copied by the adapters

If exit being called is preventing you from doing what you're trying to do, please feel free to send a PR to fix this issue. I don't know that we're likely to get to it anytime soon on our own since it doesn't affect most users

[userquin]

@benmccann I like the idea behind Astro and iles, where you have a lot of hooks, this way ppl can Just add their hooks in the plugin.

[matiasfha]

@benmccann the writeBundle hook can't read the prerendered output files in a reliable way. Looks like at the point the plugin calls this hook the previous plugin (the sveltekit one) is not yet done with it.
But, the adapt function called in closeBundle can do it.
If I write an adapter instead of a plugin the content of the files is available.
So, writing an adapter for this is not the way to go since the adapter is meant to do something different but would it be ok to add a new hook to be call before the adapter? I can do the PR but would like to check if it will be the correct path to allow users to run code before adapter to do some transformations.

[benmccann]

would it be ok to add a new hook to be call before the adapter?

I feel like adding SvelteKit hooks is not the ideal solution for this and we should instead use Vite hooks. That would allow Vite plugins to be used across projects in the Vite ecosystem and not just with SvelteKit

the writeBundle hook can't read the prerendered output files in a reliable way. Looks like at the point the plugin calls this hook the previous plugin (the sveltekit one) is not yet done with it.

It looks like that's because they're called in parallel: https://rollupjs.org/guide/en/#output-generation-hooks

So yeah, that introduces a bit of a conundrum. By default, if you do it in writeBundle you're not sure prerendering has finished and if you do it in closeBundle you're not sure that it will happen before the the adapters have run. I think perhaps the best solution might be if you added enforce: 'post' to your plugin to ensure it occurs after prerendering has finished.

I guess this is why vite-plugin-pwa has had to add a timeout to wait for prerendering to finish, which is not the cleanest solution though it allowed to get and end-to-end demo working. @userquin would you be able to remove prerenderTimeout if you add enforce: 'post' to vite-plugin-pwa?

[matiasfha]

@benmccann thanks for the answer.
I will check the timeout approach.
Just by using enforce: 'post' is not enough for this case.