-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow overriding build vite config options #3392
Conversation
🦋 Changeset detectedLatest commit: 3d61a50 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Added one small question but nothing blocking
@@ -201,7 +201,7 @@ async function clientBuild( | |||
// TODO: use vite.mergeConfig() here? | |||
info(opts.logging, null, `\n${bgGreen(black(' building client '))}`); | |||
|
|||
const viteBuildConfig = { | |||
const viteBuildConfig = vite.mergeConfig({ | |||
logLevel: 'info', | |||
mode: 'production', | |||
css: viteConfig.css, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably not important, but can css
, server
, and base
be removed here since they'll get merged in from viteConfig
?
* Allow overriding build vite config options * Adds a changeset * Test svelte * Move plugins down * Assign after for the client too * Spread output options on manually * Remove .only
How to disable css hashing? |
Changes
vite
config to override options that are used for SSR.Testing
Docs
N/A