✨ This workspace has been generated by Nx, a Smart, fast and extensible build system. ✨
To start the development server run nx serve frontend
. 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.
Nx comes with local caching already built-in (check your nx.json
). On CI you might want to go a step further.
Visit the Nx Documentation to learn more.
For removing a workspace (lib/application):
nx g rm lib-name
For creating a new react component:
nx g component my-component --project=mylib
For creating a new generator:
nx generate @nrwl/nx-plugin:generator my-generator --project=my-plugin
For rename a lib:
nx g @nrwl/workspace:mv --project my-lib --destination their-lib
For running an application:
nx serve project-name
For creating a new lib:
nx g lib
For creating a StoryBook:
nx g @nrwl/storybook:configuration project-name
For starting a storybook:
nx storybook project-name
- Links i18n keys should be suffixed with
-link
; - Buttons i18n keys should be suffixed with
-btn
; - Fields i18n keys should be suffixed with
-field
; - Placeholders i18n keys should be suffixed with
-placeholder
;
- Links i18n keys should be placed at the
links
namespace; - Fields i18n keys should be placed at the
fields
namespace; - Placeholders i18n keys should be placed at the
placeholders
namespace; - Common components i18n keys should be placed at an unique namespace suffixed with
-component
; - Page components i18n keys should be placed at an unique namespace suffixed with
-page
; - Layout components i18n keys should be placed at an unique namespace suffixed with
-layout
; - Validation errors i18n keys should be placed at the
validations
namespace;