Small vue-cli-3 fix allowing the backend pom file to copy the frontend static resources on project compilation #30
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.
I noticed that after compiling (
mvn clean install
), running the project (--projects backend spring-boot:run
) and visiting http://localhost:8088 that a blank page was shown (even though running the frontend in a dev environment it works perfectly). It turns out that the backendpom
file, which is instructed to copy assets from thefrontend/target/dist
andfrontend/target/dist/static
folders to the backendresources
folder, only copies the index.html file and not the static assets.After the recent vue-cli-3 upgrade the static assets are no longer placed in the
frontend/target/dist/static
folder, thus addingassetsDir: 'static'
to thevue.config.js
file ensures the backend can copy the static assets upon compilation.