zeus-css 1.0.10 → 1.0.11
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 -0
- package/package.json +1 -1
- package/scss/CHANGELOG.md +12 -0
package/README.md
CHANGED
|
@@ -36,6 +36,16 @@ Always import it from a single **shared/root** entry point, never from an indivi
|
|
|
36
36
|
|
|
37
37
|
**TypeScript:** `import 'zeus-css/dist/zeus.css'` needs *some* ambient `declare module '*.css'` to type-check. Next.js, Vite and Nuxt scaffolds already include this by default — nothing to do. If you're on a bare TypeScript setup and see `Cannot find module 'zeus-css/dist/zeus.css'`, running `npx zeus-css init` (step 2) creates `zeus-css-env.d.ts` for you automatically.
|
|
38
38
|
|
|
39
|
+
> ⚠️ **Step 1 and Step 2 are mutually exclusive.** Use the default import
|
|
40
|
+
> (`zeus-css/dist/zeus.css`) if you don't need custom theming. If you run
|
|
41
|
+
> `npx zeus-css init` and customize your theme, **replace** the default
|
|
42
|
+
> import with `import './zeus.theme.css'` — never use both together.
|
|
43
|
+
>
|
|
44
|
+
> ```text
|
|
45
|
+
> No customization? → import 'zeus-css/dist/zeus.css'
|
|
46
|
+
> Custom theme? → npx zeus-css init, compile, import './zeus.theme.css' (replaces the Step 1 import)
|
|
47
|
+
> ```
|
|
48
|
+
|
|
39
49
|
### 2. Customize it
|
|
40
50
|
Run the init command in the folder you want the config files in (you'll see a reminder for this after `npm install` too):
|
|
41
51
|
|
package/package.json
CHANGED
package/scss/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,18 @@ documented in [`API.md`](API.md).
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
+
## [1.0.11] — 2026-08-05
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
- **The published package's README (generated by `scripts/build-package.ts`,
|
|
13
|
+
not copied from this file) documented Step 1 (`zeus-css/dist/zeus.css`) and
|
|
14
|
+
Step 2 (`npx zeus-css init` + `zeus.theme.css`) with no statement that
|
|
15
|
+
they're mutually exclusive** — a dev following both in sequence ended up
|
|
16
|
+
with both imports in the same root layout. Added an explicit warning plus
|
|
17
|
+
a two-line flowchart between the two steps in that template, so the
|
|
18
|
+
generated README (and every future publish) states the replacement
|
|
19
|
+
relationship instead of leaving it implied.
|
|
20
|
+
|
|
9
21
|
## [1.0.10] — 2026-08-05
|
|
10
22
|
|
|
11
23
|
Published to npm as `zeus-css`. [`API.md`](API.md) documents the public API
|