This project was generated with Angular CLI version 16.2.10.

Sample steps followed:

npm install -g @angular/cli@v16-lts
ng new angular16-with-genesis-ui
? Would you like to add Angular routing? Yes
? Which stylesheet format would you like to use? CSS
...
cd angular16-with-genesis-ui
ng generate component dashboard
ng generate component not-found
ng generate module auth

In addition, moved project onto a custom webpack builder and added "skipLibCheck": true to tsconfig.json.

Please see the initial commits where these steps were broken down for clarity.

When opening the repository for the first time in either VSCode or Intellij, you should get prompted to install some recommended plugins. These include a Code Tour plugin:

• CodeTour for VSCode
• CodeTour for Intellij

After installing, you may need to manually start the "Genesis UI Integration" code tour from the menu in your IDE.

On-top of the cli generated baseline, we've configured this angular project to work with browser native Web Components, a.k.a Custom Elements, which are completely web framework independent. Angular has full support for Web Components, which you can verify on the Angular + Custom Elements Test Results, running on https://custom-elements-everywhere.com/.

To get angular to recognise Web Components, we simply add the CUSTOM_ELEMENTS_SCHEMA to the project where we need this support.

import { CUSTOM_ELEMENTS_SCHEMA, NgModule, Component } from '@angular/core';
...
@NgModule({ // < or `Component`
  ...
  schemas: [
    CUSTOM_ELEMENTS_SCHEMA
  ]
})

Then it's just a matter of adding any Web Components you wish to use to the project's dependency graph, via a <script> tag, npm install, or whatever other means you prefer.

Here we're adding a Web Component from the community via a script tag:

<script src="https://cdn.jsdelivr.net/npm/ionicons@7.2.1/dist/ionicons.js"></script>

And then adding the element markup to your templates:

<ion-icon name="rocket"></ion-icon>

That's it! No framework plumbing code required beyond perhaps binding values to these web components via their attributes, or handling their emitted events if required. Given you'll probably want to do that, you need to add the Angular FormsModule.

...
import { FormsModule } from '@angular/forms';
...
@NgModule({ // < or `Component`
  ...
  imports: [
    ...
    FormsModule  // < enable bindings etc. on our web components
  ],
})

With the above in place, our Web Components are now first class citizens. There's some Web Component binding examples at the bottom of the dashboard page.

We've added the same script tag integration to this project's index.html file, and used icon Web Component in the dashboard.component.html template. Look out for the rocket icon on the dashboard. While using the script tag approach is fine in many cases, some third-party imports may required post import setup. Where you do that setup is really up to you. If it's a component that you only want to use in one place, then perhaps import and add the setup in that area. If it's for components or design systems you plan do use across the entire application, you may wish to centralise that in a shared location. For the latter, we've created such a shared area in src/app/shared/.

Yes!

We provide a lot of pre-built and extensible Web Components at Genesis. From simple primitives, like buttons, switches, and even icon components like the above, to fully connected composites and micro frontends built to work with the Genesis backend. This project's auth module uses the pre-build @genesislcap/foundation-auth micro frontend to offload all user authentication, mfa, and self-service password recovery complexity to Genesis. Learn about these on https://learn.genesis.global/docs/web/web-components/overview/.

Beyond that, check out https://www.webcomponents.org/, where you can browse single elements and collections from well known companies such as Adobe, Github, and Google. The component.gallery and Open UI websites are also good starting points.

Angular developers who are interested in creating native Web Components should check out the Angular Elements package. Also, see the All the Ways to make a Web Component board.

Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Run ng build to build the project. The build artifacts will be stored in the dist/ directory.

Run ng test to execute the unit tests via Karma.

Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.