do not include api server plugin for production builds #275
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the default config to not add the API server plugin for production builds. This may be needed for some usecases like prerendering, but for SvelteKit apps using
@sveltejs/adapter-node
's middleware, running the server in production doesn't work because the middleware hasn't been built yet.Also cleans up the SvelteKit Node build a bit in the Gro adapter, removing unused files. The SvelteKit Node adapter is not configurable to choose between middleware and a standalone server, so the Gro adapter supports the
deploymentMode
option that defaults tomiddleware
, signalling Gro to delete the Node adapter'sindex.js
output and keepmiddlewares.js
, and vice versa whenserver
. Theboth
option deletes nothing.