feat: add compatibility with Vite 6 Environment API

[magne4000]

This is a WIP to add Environment API compatibility, by calling buildApp instead of vite.build (keeping current behaviour as default).

• new useEnvironmentAPI viteEnvironmentAPI config. Naming, location and whether it should be on the Vike CLI only -> to be discussed
• autoFullBuild is disabled in this mode
• New vike:buildApp plugins to mimic autoFullBuild

[brillout]

Thank you for opening this early; so far there aren't any conflicts with my last refactoring. I'll be merging main into this PR whenever I push refactorings to main.

[brillout]

Btw. I should be done with my refactoring soon. The bulk of it is done, it's now "only" about small things.

[brillout]

• Naming

I'd suggest viteEnvironmentAPI.

vike.dev/TODO

I guess we don't need docs for it for now. It's mostly/only going to be used by our own extensions anyways.

[brillout]

Your IDE seems to re-order imports. Can we revert these changes? We can eventually agree on some new linting rules after I merged all pending PRs & branches.

[magne4000]

Your IDE seems to re-order imports. Can we revert these changes? We can eventually agree on some new linting rules after I merged all pending PRs & branches.

Indeed, and I still don't know why, as the option is disabled :/

[magne4000]

Your IDE seems to re-order imports. Can we revert these changes? We can eventually agree on some new linting rules after I merged all pending PRs & branches.

Indeed, and I still don't know why, as the option is disabled :/

It seems like the IntelliJ Biome plugin does biome check --apply even if Run Biome check with --apply is unchecked... I'm disabling it and reverting the changes

EDIT: Issue created

[magne4000]

You can do your refactoring @brillout. I do not know how I can manage to create a unit test with vite@5 in the same monorepo. Calling vike build always use the Vite version in the linked vike package (See this issue). We could call vite build instead, but that doesn't seem really wise.

[brillout]

I see. Indeed I think we are currently not testing Vite 5 at all.

…

On Fri 7. Feb 2025 at 16:58, Joël Charles ***@***.***> wrote: You can do your refactoring @brillout <https://github.com/brillout>. I do not know how I can manage to create a unit test with ***@***.*** in the same monorepo. Calling vike build always use the Vite version in the linked vike package. We could call vite build instead, but that doesn't seem really wise. — Reply to this email directly, view it on GitHub <#2146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHVQRS4RUSY6HL4YFL3PV32OTJ2NAVCNFSM6AAAAABWTOFV6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBTGMZDONZQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[brillout]

d296d91; let me know if that's an issue.