@ojiepermana/angular 21.2.2 → 21.2.4

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.
Files changed (2) hide show
  1. package/README.md +29 -12
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -139,30 +139,47 @@ Then run:
139
139
  bun run publish
140
140
  ```
141
141
 
142
- This command rebuilds the library and publishes the generated `dist/angular` package with public access.
142
+ By default, this command publishes every configured release target from `config/release.config.json`.
143
143
 
144
- ### Standalone Brand Packages
144
+ Release targets are configured in `config/release.config.json`. Each entry can override the published
145
+ package name plus `repository`, `homepage`, and `bugs` metadata so npm shows the correct package identity.
145
146
 
146
- Brand packages now publish independently from `projects/brand/*` instead of being repackaged from the core
147
- library. The Etos package lives in `projects/brand/etos` and publishes as `@ojiepermana/etos`.
147
+ To publish the `edsis` target from that config, run:
148
148
 
149
- Consumer installation for Etos is:
149
+ ```bash
150
+ bun run publish --edsis
151
+ ```
152
+
153
+ To publish every configured release target in sequence, run:
150
154
 
151
155
  ```bash
152
- ng add @ojiepermana/angular
153
- bun add @ojiepermana/etos
156
+ bun run publish -all
154
157
  ```
155
158
 
156
- If you use `npm`, `pnpm`, or `yarn`, install the brand package with your package manager after `ng add`
157
- finishes.
159
+ `bun run publish` and `bun run publish -all` are equivalent.
160
+
161
+ That flow rebuilds `dist/angular` for each configured target, rewrites published package references, applies
162
+ the target-specific npm metadata, smoke-tests the tarball, then publishes it to npm.
163
+
164
+ ### EDSIS Verification Flow
158
165
 
159
- To build or publish the Etos package from this workspace, use:
166
+ To validate the EDSIS package locally without publishing, use:
160
167
 
161
168
  ```bash
162
- bun run build:etos
163
- bun run publish:etos
169
+ bun run build -- --package @edsis/angular --repository-url git+https://github.com/edsis/angular.git --homepage https://github.com/edsis/angular#readme --bugs-url https://github.com/edsis/angular/issues
170
+ bun run smoke:pack -- --package @edsis/angular
164
171
  ```
165
172
 
173
+ Consumer installation for the published EDSIS package is:
174
+
175
+ ```bash
176
+ ng add @edsis/angular
177
+ bun add @edsis/angular
178
+ ```
179
+
180
+ If you use `npm`, `pnpm`, or `yarn`, install the package with your package manager after `ng add`
181
+ finishes.
182
+
166
183
  ## Running unit tests
167
184
 
168
185
  To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ojiepermana/angular",
3
- "version": "21.2.2",
3
+ "version": "21.2.4",
4
4
  "repository": {
5
5
  "type": "git",
6
6
  "url": "git+https://github.com/ojiepermana/angular.git"