fix(plugin-legacy): no build.target
override on SSR build
#12171
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 very simple PR avoid the
plugin-legacy
overriding (and warning if exists) of thebuild.target
configuration for SSR.Sadly, in plugin-legacy, the
build.target
overriding (and warning if exists) happen on SSR build as well.In addition, some other plugins, like SvelteKit (together with my legacy support PR there - sveltejs/kit#6265), automatically "fixes" the build target for the SSR build, so this will eliminate the warning we get there as a side effect.
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).