✨ This workspace has been generated by Nx, a Smart, fast and extensible build system. ✨
To start the development server run nx serve shell. Open your browser and navigate to http://localhost:4200/. Happy coding!
If you happen to use Nx plugins, you can leverage code generators that might come with it.
Run nx list to get a list of available plugins and whether they have generators. Then run nx list <plugin-name> to see what generators are available.
Learn more about Nx generators on the docs.
To execute tasks with Nx use the following syntax:
nx <target> <project> <...options>
You can also run multiple targets:
nx run-many -t <target1> <target2>
..or add -p to filter specific projects
nx run-many -t <target1> <target2> -p <proj1> <proj2>
Targets can be defined in the package.json or projects.json. Learn more in the docs.
Have a look at the Nx Console extensions. It provides autocomplete support, a UI for exploring and running tasks & generators, and more! Available for VSCode, IntelliJ and comes with a LSP for Vim users.
Just run nx build demoapp to build the application. The build artifacts will be stored in the dist/ directory, ready to be deployed.
--app-background-drawer-outlet-x-button: Background color for the drawer outlet's close (X) button
Nx comes with local caching already built-in (check your nx.json). On CI you might want to go a step further.
This project uses semantic-release to automatically publish library updates based on commit messages.
We follow the Conventional Commits specification:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Scopes: ngx-liburg, ngx-liburg-icon, ngx-liburg-frame-side, repo
Examples:
feat(ngx-liburg): add new table sorting featurefix(ngx-liburg-icon): resolve icon alignment issue
Run the setup script to install necessary dependencies:
./scripts/setup-semantic-release.shWhen you push to the main branch with changes to library files, GitHub Actions will:
- Detect which libraries have changes
- Determine version bumps based on commit messages
- Update changelogs and package versions
- Publish the libraries to npm
You can also manually trigger a dry run from the GitHub Actions tab.