✨ This workspace has been generated by Nx, a Smart, fast and extensible build system. ✨
To start the development server run nx run blaunk-client:serve
|
npm run client
. Open your browser and navigate to https://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.
nx g @nrwl/next:app
nx g @nrwl/node:app
nx g @nx/next:lib --name [lib-name] --dir [lib-dir] --importPath "@li/[lib-dir]/[lib-name]"
nx g @nx/node:lib --name [lib-name] --dir [lib-dir] --importPath "@li/[lib-dir]/[lib-name]"
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 blaunk/client
to build the application. The build artifacts
will be stored in the dist/
directory, ready to be deployed.
Nx comes with local caching already built-in (check your nx.json
). On CI you
might want to go a step further.
Try to keep the code/files as close as possible. If required in another lib, then move out to the shared libs.