@ojiepermana/angular 21.1.30 → 21.2.4

package/README.md

@@ -20,6 +20,10 @@ and installed in the same flow:
 ng add @ojiepermana/angular
 ```
 
+The library requires Tailwind CSS `^4.3.0`. If the consumer workspace does
+not already have a compatible Tailwind v4 installation, `ng add` will add it
+from the published `peerDependencies`.
+
 When updating the library later, use Angular CLI as well:
 
 ```bash
@@ -31,7 +35,20 @@ companions stay aligned with the supported versions of the library.
 
 If you install the package with `npm install`, `bun add`, `pnpm add`, or `yarn
 add` directly, peer dependency installation falls back to the package
-manager's own behavior.
+manager's own behavior. In that flow, install Tailwind manually as well:
+
+```bash
+bun add @ojiepermana/angular tailwindcss@^4.3.0
+```
+
+Consumer app styles should import the library theme, Tailwind, and the
+Tailwind bridge in this order:
+
+```css
+@import '@ojiepermana/angular/theme/styles';
+@import 'tailwindcss';
+@import '@ojiepermana/angular/theme/tailwind/theme.css';
+```
 
 ## Navigation primitives
 
@@ -122,59 +139,46 @@ Then run:
 bun run publish
 ```
 
-This command rebuilds the library and publishes the generated `dist/angular` package with public access.
+By default, this command publishes every configured release target from `config/release.config.json`.
 
-### Publishing a Brand Variant
+Release targets are configured in `config/release.config.json`. Each entry can override the published
+package name plus `repository`, `homepage`, and `bugs` metadata so npm shows the correct package identity.
 
-Brand variants let the same library publish under another scoped package while keeping only one selected
-folder from `projects/angular/brand`. Shared entrypoints such as `chart`, `component`, `generator`,
-`layout`, `navigation`, and `theme` are still built for every variant.
+To publish the `edsis` target from that config, run:
 
-Configure variants in `projects/angular/scripts/package-variants.json`:
-
-```json
-{
-  "sourcePackageName": "@ojiepermana/angular",
-  "variants": {
-    "edsis": {
-      "packageName": "@edsis/angular",
-      "brandId": "etos"
-    }
-  }
-}
+```bash
+bun run publish --edsis
 ```
 
-If `brandId` is omitted, it defaults to the npm scope. For example, `@edsis/angular` uses
-`projects/angular/brand/edsis`.
-
-Publish a configured variant with:
+To publish every configured release target in sequence, run:
 
 ```bash
-bun run publish:variant edsis bug
+bun run publish -all
 ```
 
-The bump accepts `major`, `minor`, `patch`, `bug`, or `bugs`; `bug` and `bugs` are aliases for a patch
-version bump. Use `--dry-run` to build and smoke-test the variant without committing, pushing, or
-publishing:
+`bun run publish` and `bun run publish -all` are equivalent.
+
+That flow rebuilds `dist/angular` for each configured target, rewrites published package references, applies
+the target-specific npm metadata, smoke-tests the tarball, then publishes it to npm.
+
+### EDSIS Verification Flow
+
+To validate the EDSIS package locally without publishing, use:
 
 ```bash
-bun run publish:variant edsis bug --dry-run
+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
+bun run smoke:pack -- --package @edsis/angular
 ```
 
-To add a future brand such as `@ala/angular`, create `projects/angular/brand/ala`, add an `ala` entry to
-`package-variants.json`, then run `bun run publish:variant ala bug`. A new npm script is not required
-unless you want a shortcut.
-
-If the package scope must differ from the folder name, map it at publish time with `--path`. For example,
-if the Etos source must be published as `@edsis/angular`, run:
+Consumer installation for the published EDSIS package is:
 
 ```bash
-bun run publish:variant edsis bug --path=etos
+ng add @edsis/angular
+bun add @edsis/angular
 ```
 
-This builds package `@edsis/angular` from `projects/angular/brand/etos`, so the brand entrypoint resolves
-as `@edsis/angular/etos`. If the bump is omitted, the script prompts for `major`, `minor`, `patch`, or
-`bug`.
+If you use `npm`, `pnpm`, or `yarn`, install the package with your package manager after `ng add`
+finishes.
 
 ## Running unit tests