refactor(adapters): modify build scripts to include additional vite b…

[JerryWu1234]

…uild step

The build scripts in all adapters' package.json files were updated to include an additional vite build step before the existing build command. This ensures a more robust build process by performing a standard build before the adapter-specific build.

What is it?

fixes #7479

• Feature / enhancement
• Bug
• Docs / tests / types / typos
• Infra

Description

Checklist

• My code follows the developer guidelines of this project
• I performed a self-review of my own code
• I added a changeset with pnpm change
• I made corresponding changes to the Qwik docs
• I added new tests to cover the fix / functionality

[changeset-bot]

🦋 Changeset detected

Latest commit: 0866fc4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@builder.io/qwik-city	Major
@builder.io/qwik	Major
eslint-plugin-qwik	Major
create-qwik	Major

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@builder.io/qwik@7504

npm i https://pkg.pr.new/@builder.io/qwik-city@7504

npm i https://pkg.pr.new/eslint-plugin-qwik@7504

npm i https://pkg.pr.new/create-qwik@7504

commit: bebc3f7

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
qwik-docs	✅ Ready (View Log)	Visit Preview	bebc3f7

[wmertens]

The problem is that when you run build.server, you're supposed to know what you're doing. Otherwise, you would just run build.

By doing the client build twice you're making things slower for everyone.

So I cannot accept this PR, but if it is really necessary to make sure client is up to date, perhaps a command can be added to qwik-cli to check that that is so and print a warning.

For example qwik check-client => no output or client build is missing or client build is older than the source code.

[JerryWu1234]

The problem is that when you run build.server, you're supposed to know what you're doing. Otherwise, you would just run build.

By doing the client build twice you're making things slower for everyone.

So I cannot accept this PR, but if it is really necessary to make sure client is up to date, perhaps a command can be added to qwik-cli to check that that is so and print a warning.

For example qwik check-client => no output or client build is missing or client build is older than the source code.

The problem is that when you run build.server, you're supposed to know what you're doing. Otherwise, you would just run build.

By doing the client build twice you're making things slower for everyone.

So I cannot accept this PR, but if it is really necessary to make sure client is up to date, perhaps a command can be added to qwik-cli to check that that is so and print a warning.

For example qwik check-client => no output or client build is missing or client build is older than the source code.

@wmertens
I have different ideas about this.
Could we check if the use has a directory named disk after running qwik add?
and we throw a warning or help user to run build