@wolkabout/commons 0.0.4 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -56
- package/fesm2022/wolkabout-commons.mjs +6866 -13
- package/fesm2022/wolkabout-commons.mjs.map +1 -1
- package/index.d.ts +1499 -8
- package/package.json +19 -3
- package/fesm2022/commons.mjs +0 -23
- package/fesm2022/commons.mjs.map +0 -1
package/README.md
CHANGED
|
@@ -1,63 +1,17 @@
|
|
|
1
|
-
|
|
1
|
+
Build
|
|
2
|
+
-
|
|
3
|
+
Don't forget to increase the version before building.
|
|
4
|
+
The version is in `projects/commons/package.json`, and not the main one.
|
|
2
5
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
## Code scaffolding
|
|
6
|
-
|
|
7
|
-
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
|
|
8
|
-
|
|
9
|
-
```bash
|
|
10
|
-
ng generate component component-name
|
|
11
|
-
```
|
|
12
|
-
|
|
13
|
-
For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:
|
|
14
|
-
|
|
15
|
-
```bash
|
|
16
|
-
ng generate --help
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
## Building
|
|
20
|
-
|
|
21
|
-
To build the library, run:
|
|
22
|
-
|
|
23
|
-
```bash
|
|
6
|
+
```shell
|
|
24
7
|
ng build commons
|
|
25
8
|
```
|
|
26
9
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
### Publishing the Library
|
|
30
|
-
|
|
31
|
-
Once the project is built, you can publish your library by following these steps:
|
|
32
|
-
|
|
33
|
-
1. Navigate to the `dist` directory:
|
|
34
|
-
```bash
|
|
35
|
-
cd dist/commons
|
|
36
|
-
```
|
|
37
|
-
|
|
38
|
-
2. Run the `npm publish` command to publish your library to the npm registry:
|
|
39
|
-
```bash
|
|
40
|
-
npm publish
|
|
41
|
-
```
|
|
42
|
-
|
|
43
|
-
## Running unit tests
|
|
44
|
-
|
|
45
|
-
To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:
|
|
46
|
-
|
|
47
|
-
```bash
|
|
48
|
-
ng test
|
|
49
|
-
```
|
|
50
|
-
|
|
51
|
-
## Running end-to-end tests
|
|
10
|
+
Publish to NPM
|
|
11
|
+
-
|
|
52
12
|
|
|
53
|
-
|
|
13
|
+
**Important**: Run from `/dist/commons` folder!
|
|
54
14
|
|
|
55
|
-
```
|
|
56
|
-
|
|
15
|
+
```shell
|
|
16
|
+
npm publish
|
|
57
17
|
```
|
|
58
|
-
|
|
59
|
-
Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
|
|
60
|
-
|
|
61
|
-
## Additional Resources
|
|
62
|
-
|
|
63
|
-
For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
|