test: run npm production tests before development mode (23.5) #20951
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the dev and prod mode test modules are defined in the same folder, the production mode can fail if executed after development mode. This happens because the dev mode npm install background process may still be running when Maven executes the frontend build for prod mode, causing conflicts in the node_modules folder. This change swaps the execution order of the modules to ensure that prod mode is executed before dev mode.
|
caalador
approved these changes
Feb 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the dev and prod mode test modules are defined in the same folder, the production mode can fail if executed after development mode. This happens because the dev mode npm install background process may still be running when Maven executes the frontend build for prod mode, causing conflicts in the node_modules folder.
This change swaps the execution order of the modules to ensure that prod mode is executed before dev mode.