@everchron/ec-shards 22.0.1 → 22.1.0
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 +24 -1
- package/dist/ec-shards.cjs +1 -1
- package/dist/ec-shards.css +1 -1
- package/dist/ec-shards.js +32 -17
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -26,10 +26,33 @@ Expected node version: `>= 24.13.0`
|
|
|
26
26
|
| `npm run dev` | Compiles and hot-reloads for app development |
|
|
27
27
|
| `npm run build` | Compiles, minifies, and builds package |
|
|
28
28
|
| `npm run test` | Run Unit Tests with [Vitest](https://vitest.dev/) |
|
|
29
|
-
| `npm publish --access public` | Publishes built package to npm (main branch). **Note:** You must be logged into npm with an account that has access to the @everchron organization. Additionally, you need to bump the version number in `package.json` before publishing. |
|
|
29
|
+
| `npm publish --access public` | Publishes built package to npm (main branch). **Note:** You must be logged into npm with an account that has access to the @everchron organization. Details below. Additionally, you need to bump the version number in `package.json` before publishing. |
|
|
30
30
|
| `npm publish --access public --tag beta` | Published built package to npm with a feature/branch tag |
|
|
31
31
|
| `npm run check-icons` | Process all icons in the `src/assets/icons` directory (removes hardcoded colors and adds `vector-effect="non-scaling-stroke"`) |
|
|
32
32
|
|
|
33
|
+
### Logging into npm via CLI
|
|
34
|
+
|
|
35
|
+
Being logged into npmjs.com in your browser does not authenticate the npm CLI. If `npm publish` fails with a `404 Not Found` (or `npm whoami` returns `401 Unauthorized`), your CLI session is missing or expired.
|
|
36
|
+
|
|
37
|
+
1. Log in (opens the browser to complete authentication):
|
|
38
|
+
```bash
|
|
39
|
+
npm login
|
|
40
|
+
```
|
|
41
|
+
2. Verify you're authenticated:
|
|
42
|
+
```bash
|
|
43
|
+
npm whoami
|
|
44
|
+
```
|
|
45
|
+
3. Confirm you have publish rights (your username should be listed as `read-write`):
|
|
46
|
+
```bash
|
|
47
|
+
npm access list collaborators @everchron/ec-shards
|
|
48
|
+
```
|
|
49
|
+
4. Publish (add `--otp=<code>` if your account uses 2FA):
|
|
50
|
+
```bash
|
|
51
|
+
npm publish --access public
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
CLI login sessions expire, so you may need to run `npm login` again before future publishes. If `npm whoami` succeeds but publishing still returns 404, ask an `@everchron` org owner to grant you write access.
|
|
55
|
+
|
|
33
56
|
## Recommended IDE Setup
|
|
34
57
|
|
|
35
58
|
[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).
|