Vaadin started with default production mode after bumping version

Hi!

Couple hours ago I bumped vaadin in my project from 24.3.2 to 24.4.11 (and spring-boot from 3.2.4 to 3.3.3. if it matters).

I ran build-frontend, started the app and it failed with a “Vite build exited with a non zero status”, but I couldn’t get to the error fast enough because of the java exceptions filling up the console.

I decided to clean and try again, so I ran these in order:

mvn clean vaadin:clean-frontend
// then deleted package-lock.json package.json tsconfig.json types.d.ts vite.config.ts vite.generated.ts
mvn -DskipTests install
mvn vaadin:build-frontend
// meanwhile npm installed required packages
mvn spring-boot:run

And it failed again with “Vite build exited with a non zero status”, but this time I managed to catch the build error, which was referring to a module installed incorrectly (I think).

Failed to resolve entry for package "@remix-run/router"

So I decided to delete node_modules from my project, then ran:

mvn -DskipTests install
mvn vaadin:build-frontend
// meanwhile npm installed required packages again

Then started the app and it worked, but for some reason it started in production mode instead of default development mode and I don’t know why.

Did you change the default mode in any 24.4.X ?
How can I switch back to development mode?
I didn’t find any flow-build-info.json or enableDevServer parameter (I think you deprecated this in 24.4.7 ?).

PS: Preview mode before posting in this forum would be a great addition, in my opinion.

The build-frontend goal always builds a production mode artifact. Nothing has changed in regard since 24.3.

To run the application in dev mode, simply clean the target folder (e.g. mvn clean) and start without calling build-frontend