@deepersignals/components v1.0.2

DsComponents

This library was generated with Angular CLI version 15.1.0.

Code scaffolding

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

Note: Don't forget to add --project @deepersignals/components or else it will be added to the default project in your angular.json file.

Build

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

Publishing

After building your library with ng build @deepersignals/components, go to the dist folder cd dist/deepersingnals/components and run npm publish.

Running unit tests

Run ng test ds-components to execute the unit tests via Karma.

Developing and testing in local application

When developing and testing this library in ds-app, I have found the following options the easiest way to work:

1. in angular.json set "aot": false, & "buildOptimizer": false,
2. set the following in the apps tsconfig.ts:

"paths": {
      "@deepersignals/components": ["path/to/local/ds-components/ds-workspace/projects/deepersignals/components*"]
    }

3. disable cache ng cache disable (note, you can leave cache on, but you would need to run ng cache clean after running a build on the linked component library)
4. link library through npm link

---me : npm link ../ds-tailwind-components/dist/deepersignals/components