@siyahi/ui 0.1.1-next.1 → 0.1.1-next.2
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 +4 -17
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -49,24 +49,11 @@ and the Recharts pieces charts are built from. Add `lucide-react` only if your
|
|
|
49
49
|
own code imports icons. A Next.js app compiles the same stylesheet through
|
|
50
50
|
`@tailwindcss/postcss` instead of the Vite plugin.
|
|
51
51
|
|
|
52
|
-
###
|
|
52
|
+
### Also on GitHub releases
|
|
53
53
|
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
above:
|
|
58
|
-
|
|
59
|
-
```sh
|
|
60
|
-
npm install --allow-remote=root https://github.com/jatinbansal1998/siyahi/releases/download/v<version>/siyahi-ui-<version>.tgz
|
|
61
|
-
npm install --allow-remote=root --save-dev https://github.com/jatinbansal1998/siyahi/releases/download/v<version>/siyahi-tools-<version>.tgz
|
|
62
|
-
```
|
|
63
|
-
|
|
64
|
-
npm 12 refuses tarball URLs unless `allow-remote` permits them; put
|
|
65
|
-
`allow-remote=root` in the project's `.npmrc` so a later plain `npm install`
|
|
66
|
-
works too. The rolling `next` release always holds the newest build under fixed
|
|
67
|
-
names (`.../releases/download/next/siyahi-ui-next.tgz` and
|
|
68
|
-
`siyahi-tools-next.tgz`); its assets are replaced on every merge, so pin a
|
|
69
|
-
versioned URL in `package.json`.
|
|
54
|
+
Every merge to `main` also attaches both tarballs to a GitHub release
|
|
55
|
+
(`v<version>`, plus a rolling `next`). They are a fallback if npm is unreachable:
|
|
56
|
+
`npm install --allow-remote=root https://github.com/jatinbansal1998/siyahi/releases/download/v<version>/siyahi-ui-<version>.tgz`.
|
|
70
57
|
|
|
71
58
|
## What is in it
|
|
72
59
|
|