@zenit-hosting/zenit-ui 0.2.0 → 0.2.2

package/llms-full.txt

@@ -1,6 +1,6 @@
 # zenit-ui — complete reference
 
-> Version 0.2.0. Everything needed to use this library correctly, with no other file and
+> Version 0.2.2. Everything needed to use this library correctly, with no other file and
 > no access to its sources. Generated from the sources; do not edit by hand.
 
 ## Contents
@@ -76,12 +76,14 @@ is no `NgModule` and no `forRoot`.
 
 ## 3. Setup
 
-1. **Install.** The package is not on npm; it is installed from the tarball built by
-   `npm pack` inside `dist/zenit-ui`:
+1. **Install.** The package is `@zenit-hosting/zenit-ui` on npmjs.org. Install it under the
+   alias `zenit-ui`, so imports and stylesheet paths stay `zenit-ui`:
    ```bash
-   npm i ./zenit-ui-0.2.0.tgz
+   npm install zenit-ui@npm:@zenit-hosting/zenit-ui@^0.2.2
    ```
-   `ng add ./zenit-ui-0.2.0.tgz --themes` performs steps 2 to 6 automatically.
+   Never `npm i zenit-ui` or `ng add zenit-ui`: the unscoped name belongs to somebody else.
+   `ng generate zenit-ui:ng-add --themes` then performs steps 2 to 6 automatically (not
+   `ng add`, which would add the package a second time without the alias).
 
 2. **Register the stylesheets** in `angular.json` (`projects.<app>.architect.build.options.styles`)
    or via `@import` in your entry stylesheet. The order is binding:
@@ -4136,7 +4138,7 @@ The stylesheet has to block rendering as well. The Angular CLI inlines
 "critical" CSS and loads the rest late; `[data-theme="light"]` is never
 critical, because nothing in `index.html` matches it. Set
 `optimization.styles.inlineCritical` to `false` in the `production`
-configuration of the build target; `ng add zenit-ui --themes` writes both
+configuration of the build target; `ng generate zenit-ui:ng-add --themes` writes both
 the script and that setting.
 
 With a Content Security Policy the returned string is what you hash

package/llms.txt

@@ -1,6 +1,6 @@
 # zenit-ui
 
-> Component library 0.2.0 for Angular 22 of the Zenit design system:
+> Component library 0.2.2 for Angular 22 of the Zenit design system:
 > 84 standalone components and directives, dark by default, token-driven,
 > `@angular/cdk` for overlays and no Angular Material anywhere. This file is the index;
 > `llms-full.txt` next to it is the complete reference and needs no other file.
@@ -42,7 +42,8 @@ Business logic, routes and copy stay in your application.
 
 ## Setup in 6 steps
 
-1. `npm i ./zenit-ui-0.2.0.tgz` (the package is not on npm). `ng add ./zenit-ui-0.2.0.tgz --themes`
+1. `npm install zenit-ui@npm:@zenit-hosting/zenit-ui@^0.2.2` (the alias keeps the import
+   path `zenit-ui`; never install the unscoped `zenit-ui`). `ng generate zenit-ui:ng-add --themes`
    does steps 2 to 6 for you.
 2. Register the stylesheets in `angular.json`, in this order:
    `zenit-ui/styles/tokens.css`, `@angular/cdk/overlay-prebuilt.css`,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zenit-hosting/zenit-ui",
-  "version": "0.2.0",
-  "license": "UNLICENSED",
+  "version": "0.2.2",
+  "license": "MIT",
   "publishConfig": {
     "access": "public"
   },

package/schematics/ng-add/index.js

@@ -5,7 +5,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ngAdd = ngAdd;
 /**
- * `ng add zenit-ui`.
+ * the `ng-add` schematic.
  *
  * Performs the setup that `projects/zenit-ui/README.md` documents by hand:
  * style entries in `angular.json`, `z-root` in `index.html`, `@angular/cdk`,

package/schematics/ng-add/init-script.js

@@ -1,6 +1,6 @@
 "use strict";
 /*
- * Plain TypeScript without a single import, on purpose: `ng add zenit-ui`
+ * Plain TypeScript without a single import, on purpose: the `ng-add` schematic
  * needs the same script, and schematics are compiled apart from the library
  * (CommonJS, no DOM types, `rootDir: schematics`). A byte-identical copy of
  * this file therefore lives at `schematics/ng-add/init-script.ts`; the test in
@@ -86,7 +86,7 @@ function alsLiteral(wert) {
  * "critical" CSS and loads the rest late; `[data-theme="light"]` is never
  * critical, because nothing in `index.html` matches it. Set
  * `optimization.styles.inlineCritical` to `false` in the `production`
- * configuration of the build target; `ng add zenit-ui --themes` writes both
+ * configuration of the build target; `ng generate zenit-ui:ng-add --themes` writes both
  * the script and that setting.
  *
  * With a Content Security Policy the returned string is what you hash

package/types/zenit-hosting-zenit-ui.d.ts

@@ -5733,7 +5733,7 @@ interface ZThemeInitConfig {
  * "critical" CSS and loads the rest late; `[data-theme="light"]` is never
  * critical, because nothing in `index.html` matches it. Set
  * `optimization.styles.inlineCritical` to `false` in the `production`
- * configuration of the build target; `ng add zenit-ui --themes` writes both
+ * configuration of the build target; `ng generate zenit-ui:ng-add --themes` writes both
  * the script and that setting.
  *
  * With a Content Security Policy the returned string is what you hash