Have a look at the Makefile to find the most used dev commands.
In one terminal tab, use this command to start backend in dev mode (on: http://0.0.0.0:8080).
make dev-api
Or use those command to start the api in packaged mode (on: http://0.0.0.0:8080).
make build-api
make start-api
In the another terminal tab, use those commands to link the library and then start frontend in dev mode also watching for changes in the lib (on: http://0.0.0.0:3000).
make link-lib
make dev-lib
If you want to unlink the local library and use the npm package library in the frontend:
make unlink-lib
- https://www.npmjs.com/package/@quarkusio/code-quarkus.components
- https://www.npmjs.com/package/@quarkusio/code-quarkus.core.analytics
- https://www.npmjs.com/package/@quarkusio/code-quarkus.core.components
- https://www.npmjs.com/package/@quarkusio/code-quarkus.core.types
On your PR which contains the changes, run (before committing):
make tag-lib
It will automatically change the .bitmap file, which will trigger a GH action when the PR gets merged to publish a new version in npm.
Staging is auto-updated with main (it takes ~15min to refresh after a merge): https://stage.code.quarkus.io
You can check deployed commit hash on: https://stage.code.quarkus.io/api/config
It is automated based on the acceptance tests