@minicode-dev/chat 0.1.0 → 0.1.2

package/README.md

@@ -1,15 +1,17 @@
 # @minicode-dev/chat
 
 Real-time chat for React (WebSocket, reactions, editing, emoji, GIFs/stickers via KLIPY, file and voice
-attachments, notifications, Connect 4 and 3D Battleship) extracted from LIRA.
+attachments, notifications, Connect 4 and 3D Battleship).
 
-- Owner: **Minicode** · Project: **LIRA** · License: UNLICENSED (private, internal use only).
-- Migration plan and status: `docs/MBSoft-Chat-NPM-Migration.md` in the LIRA repository.
+Standalone, reusable npm package for integration into React applications through configurable
+providers and transport adapters.
 
-## Installation (private registry)
+- Owner: **Minicode** · License: `UNLICENSED`.
 
-The package is published as a **restricted** package under the `@minicode-dev` scope. Add an `.npmrc` to the
-host project (keep the token out of git, e.g. via an environment variable):
+## Installation
+
+Install the package from npm. If your registry requires authentication, configure an `.npmrc` in
+the host project (keep the token out of git, e.g. via an environment variable):
 
 ```ini
 @minicode-dev:registry=https://registry.npmjs.org/
@@ -69,7 +71,7 @@ export function ChatRoute() {
 }
 ```
 
-- `LiraChatProvider` props: `config`, `transport` (inject your own `ChatTransport`, e.g. the LIRA adapter;
+- `LiraChatProvider` props: `config`, `transport` (inject your own `ChatTransport` adapter;
   the provider never closes an injected transport), `stores`, `chatStore` and `children`. Without a
   `transport`, a standalone WebSocket transport is created from `config.websocket.url`.
 - `ChatWindow` props: `placement` (`'floating' | 'modal' | 'embedded'`), `open` / `onOpenChange`
@@ -111,14 +113,52 @@ from `/sounds/...`. Either:
 
 The files are also exposed as `@minicode-dev/chat/assets/*` for bundlers that can import asset URLs.
 
-## Development (LIRA workspace)
+## Local development
 
-Inside the LIRA repo the package lives in `packages/chat` and is consumed **from source** through the
-aliases in the root `vite.config.js`. The exports also carry a custom `@minicode-dev/source` condition that
-points at `src/` for tooling that opts into it (`resolve.conditions`); it is never resolved by default.
+This repository builds a library; it does not include a standalone demo or a `dev` script.
 
 ```bash
-npm run build:chat          # vite library build -> packages/chat/dist (index.js + styles.css)
-npm pack -w @minicode-dev/chat  # runs prepack (build) and creates the tarball
-npm publish -w @minicode-dev/chat
+npm install
+npm run build  # ESM library and styles in dist/
+npm pack       # builds again via prepack and creates an installable .tgz
 ```
+
+To test local changes, install the generated tarball in a React application:
+
+```bash
+# Run inside your consuming application; adjust the path and package version.
+npm install /path/to/minicode-chat/minicode-dev-chat-0.1.0.tgz
+npm run dev # if your application provides this script
+```
+
+Repeat packing and installation after changes. Installation updates the consuming application's
+local dependency files. Real-time messaging requires a compatible WebSocket service and any
+necessary authentication, supplied by the consuming application.
+
+For source-based development, the custom `@minicode-dev/source` export condition points at `src/`.
+Tooling must explicitly enable it (for example through Vite's `resolve.conditions`) and resolve
+this local package. It is not enabled by default; React and other shared peers must resolve to
+one copy in the consuming application.
+
+## Publishing updates
+
+Log in yourself with `npm login`, then run:
+
+```bash
+npm run release                 # patch version, build, validate contents, publish
+npm run release -- minor        # minor version
+npm run release -- major        # major version
+npm run release -- --dry-run    # build and inspect; no version change or publication
+```
+
+The release script checks your npm session, builds, increments the version without
+creating a Git commit or tag, and validates the exact archive before publishing it.
+Only `dist/`, `assets/`, public types, README, changelog and package metadata are allowed.
+Temporary archives and this package's root `.tgz` files are removed even on failure.
+Build output in `dist/` is retained for local use. If publication fails after the
+version bump, the updated version remains in `package.json` and the lockfile.
+Registry access follows `publishConfig` in `package.json`; login and any required
+npm authentication challenge are handled by you. No Git push is performed.
+
+The command is named `release` because npm reserves `publish` as a lifecycle hook;
+a script with that name that calls `npm publish` could invoke itself recursively.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@minicode-dev/chat",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "private": false,
   "description": "LIRA real-time chat (WebSocket, media, games) as a React package.",
   "author": "Minicode",
@@ -40,7 +40,8 @@
   ],
   "scripts": {
     "build": "vite build",
-    "prepack": "npm run build"
+    "prepack": "npm run build",
+    "release": "node scripts/release.mjs"
   },
   "peerDependencies": {
     "lucide-react": ">=0.400.0",
@@ -59,7 +60,7 @@
     "emojibase-data": "^17.0.0"
   },
   "publishConfig": {
-    "access": "restricted"
+    "access": "public"
   },
   "devDependencies": {
     "@vitejs/plugin-react-swc": "^4.3.3",