quadqr-js 1.0.0 → 1.0.1

package/README.md

@@ -593,7 +593,7 @@ console.log(result.text);
 The `quadqr-js` package can be loaded directly from npm-backed CDNs:
 
 ```html
-<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/quadqr.min.js"></script>
+<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.1/dist/quadqr.min.js"></script>
 <script>
   const code = QuadQR.encodeText("Hello from a script tag");
 </script>

package/docs/BROWSER_CDN.md

@@ -83,7 +83,7 @@ The global browser build exposes `window.QuadQR` / `globalThis.QuadQR`.
 
 ```html
 <canvas id="qr"></canvas>
-<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/quadqr.min.js"></script>
+<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.1/dist/quadqr.min.js"></script>
 <script>
   const code = QuadQR.encodeText("Hello CDN");
 
@@ -97,7 +97,7 @@ The global browser build exposes `window.QuadQR` / `globalThis.QuadQR`.
 ## unpkg
 
 ```html
-<script src="https://unpkg.com/quadqr-js@1.0.0/dist/quadqr.min.js"></script>
+<script src="https://unpkg.com/quadqr-js@1.0.1/dist/quadqr.min.js"></script>
 ```
 
 ## Direct CDN ESM
@@ -107,7 +107,7 @@ The global browser build exposes `window.QuadQR` / `globalThis.QuadQR`.
   import {
     encodeText,
     renderToCanvas
-  } from "https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/browser.js";
+  } from "https://cdn.jsdelivr.net/npm/quadqr-js@1.0.1/dist/browser.js";
 
   const code = encodeText("ES module CDN");
   renderToCanvas(code, document.querySelector("#qr"));
@@ -134,4 +134,4 @@ WASM is optional. The normal JavaScript implementation remains available if it c
 
 ## Production recommendation
 
-Pin a concrete package version such as `@1.0.0` in CDN URLs so an existing site does not silently change when a newer package version becomes available.
+Pin a concrete package version such as `@1.0.1` in CDN URLs so an existing site does not silently change when a newer package version becomes available.

package/docs/GETTING_STARTED.md

@@ -147,7 +147,7 @@ PNG generation and decoding are built into the Node.js adapter.
 
 ```html
 <canvas id="qr"></canvas>
-<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/quadqr.min.js"></script>
+<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.1/dist/quadqr.min.js"></script>
 <script>
   const code = QuadQR.encodeText("No build step");
   QuadQR.renderToCanvas(code, document.querySelector("#qr"));

package/docs/WASM.md

@@ -56,7 +56,7 @@ You can also provide WASM bytes directly through the `bytes` option.
 When the classic `quadqr.min.js` global build is loaded from a CDN, `QuadQR.initWasm()` resolves the bundled sibling WASM asset from the same package/version location.
 
 ```html
-<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/quadqr.min.js"></script>
+<script src="https://cdn.jsdelivr.net/npm/quadqr-js@1.0.1/dist/quadqr.min.js"></script>
 <script>
   await QuadQR.initWasm();
 </script>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "quadqr-js",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "QuadQR: experimental four-state RGBW matrix code with Spectrum ECC, browser/Node scanning, CDN builds, and optional AES-256-GCM secure payloads.",
   "type": "module",
   "main": "./dist/index.cjs",

package/docs/PUBLISHING.md

@@ -1,109 +0,0 @@
-# Publishing QuadQR to npm
-
-QuadQR is published on npm as [`quadqr-js`](https://www.npmjs.com/package/quadqr-js). The repository package name is `quadqr-js`.
-
-The QuadQR project/brand, browser global (`QuadQR`), CLI executable (`quadqr`), and generated filenames remain unchanged. Only the npm package identifier is `quadqr-js`.
-
-## 1. Create/sign in to npm
-
-Create an account at https://www.npmjs.com/ and enable two-factor authentication.
-
-Then authenticate the CLI:
-
-```bash
-npm login
-```
-
-Check the active account:
-
-```bash
-npm whoami
-```
-
-## 2. Install repository dependencies
-
-QuadQR currently has no runtime dependencies, but run:
-
-```bash
-npm install
-```
-
-so your local package lock and npm metadata are synchronized.
-
-## 3. Verify the package metadata
-
-```bash
-npm view quadqr-js
-```
-
-Confirm the published package and current version before releasing an update.
-
-## 4. Run the full release checks
-
-```bash
-npm test
-npm run benchmark
-npm run pack:check
-```
-
-`pack:check` rebuilds `dist/` and displays exactly what npm will include.
-
-You can inspect the final tarball too:
-
-```bash
-npm pack
-```
-
-## 5. Publish
-
-The package is an unscoped public package and `publishConfig.access` is already set to `public`, so publish with:
-
-```bash
-npm publish
-```
-
-npm publishing requires an account that satisfies npm's current 2FA/authentication requirements.
-
-## 6. Verify installation from a clean directory
-
-```bash
-mkdir quadqr-consumer-test
-cd quadqr-consumer-test
-npm init -y
-npm install quadqr-js
-```
-
-Then test ESM, Node PNG, and the CLI.
-
-```bash
-npx quadqr-js keygen
-npx quadqr-js encode "Hello from npm" -o hello.png
-npx quadqr-js decode hello.png
-```
-
-## 7. Verify CDN availability
-
-After npm and CDN caches update, test:
-
-```text
-https://cdn.jsdelivr.net/npm/quadqr-js@1.0.0/dist/quadqr.min.js
-https://unpkg.com/quadqr-js@1.0.0/dist/quadqr.min.js
-```
-
-Then call `QuadQR.encodeText(...)` from a plain HTML page.
-
-## Releasing the next version
-
-Use semantic versioning:
-
-```bash
-npm version patch
-# or
-npm version minor
-# or
-npm version major
-```
-
-Then run the release checks again and publish.
-
-Never reuse an npm version that has already been published. Published package versions are immutable.