@chidchanun/bcp 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -2,6 +2,26 @@
 
 All notable framework changes are tracked here before release.
 
+## 0.1.2 - SSR Link hotfix
+
+### Client routing
+
+- Export `Link` through an SSR-safe implementation that uses `React.createElement` semantics without relying on a global `React` binding.
+- Avoid the `ReferenceError: React is not defined` failure when a published BCP package is executed through `tsx` from `node_modules` during server-side rendering.
+- Added an SSR regression test that renders the public `Link` component with `react-dom/server`.
+
+## 0.1.1 - Packaging hotfix
+
+### Packaging and release recovery
+
+- Preserve the `bcp` executable in npm package metadata by using npm-normalized `bin` paths.
+- Preserve the `create-bcp-app` executable with the same normalized `bin` convention.
+- Clean-install smoke tests now verify the actual executables created in `node_modules/.bin` and execute the installed `bcp` CLI through an npm script.
+- Partial-release recovery no longer runs publish dry-runs against versions that already exist on npm.
+- Resume mode skips package versions already accepted by npm and continues with the missing package.
+- Successful publishes can be confirmed by the selected npm dist-tag while registry/security processing is still delaying normal version visibility.
+- Added explicit `release:publish:yes` and `release:resume` scripts so publish confirmation does not depend on npm argument forwarding.
+
 ## 0.1.0 - Pre-release
 
 ### Framework core

package/docs/releasing.md

@@ -4,7 +4,7 @@ The source repository is a private npm workspace package for development. Releas
 
 BCP Framework and `create-bcp-app` are prepared for public release under the MIT License. Normal build and test tooling never performs a real `npm publish` automatically. The dedicated release publish command requires explicit confirmation and a matching Git tag.
 
-The selected public npm identities for the first release are:
+The selected public npm identities are:
 
 ```text
 @chidchanun/bcp
@@ -18,7 +18,7 @@ Application source continues importing from `bcp`. `create-bcp-app` stores the s
 Use the version helper instead of editing package metadata manually:
 
 ```bash
-npm run version:set -- 0.1.0
+npm run version:set -- 0.1.1
 ```
 
 It synchronizes the release version across:
@@ -43,13 +43,15 @@ This runs type checking, the complete unit/integration/E2E/package test suite, t
 - synchronized semver metadata
 - required documentation
 - MIT license metadata and license files
-- staged public package exports
+- staged public package exports and executable metadata
 - public npm access configuration
 - exact `v<version>` matching when the check runs from a Git tag
 
+The package smoke test performs clean installs from packed tarballs and verifies that npm actually creates the `bcp` and `create-bcp-app` executables in `node_modules/.bin`.
+
 ## 3. Verify npm package names and ownership
 
-Before the first publish, authenticate to npm:
+Authenticate to npm before publishing:
 
 ```bash
 npm login
@@ -62,7 +64,7 @@ Then run:
 npm run release:name-check
 ```
 
-The default RC package names are now locked by `scripts/release-env.mjs` to:
+The default RC package names are locked by `scripts/release-env.mjs` to:
 
 ```text
 @chidchanun/bcp
@@ -108,7 +110,7 @@ The gate fails when:
 - `<package>@<local-version>` already exists and therefore cannot be republished
 - the local version is older than or equal to the registry's current latest version
 
-Because `@chidchanun/bcp` and `create-bcp-app` are new package names at the time of the first RC check, `0.1.0` is valid as their initial release version unless either name/version is published before the release completes.
+A published npm version is immutable. If a packaging defect is discovered after publication, increment the patch version instead of trying to replace the existing version.
 
 ## 5. Run npm publish dry-run and clean-install smoke
 
@@ -116,7 +118,7 @@ Because `@chidchanun/bcp` and `create-bcp-app` are new package names at the time
 npm run release:dry-run
 ```
 
-This performs `npm publish --dry-run` for both staged packages, packs fresh tarballs, installs the framework tarball into a temporary clean project, executes the installed BCP CLI, installs the `create-bcp-app` tarball separately, and generates another temporary app from the installed generator.
+This performs `npm publish --dry-run` for both staged packages, packs fresh tarballs, installs the framework tarball into a temporary clean project, verifies the installed `bcp` executable, installs the `create-bcp-app` tarball separately, and verifies its generated executable.
 
 No package is uploaded to the npm registry.
 
@@ -190,7 +192,7 @@ A generated application's `package.json` should therefore contain a dependency e
 ```json
 {
   "dependencies": {
-    "bcp": "npm:@chidchanun/bcp@^0.1.0"
+    "bcp": "npm:@chidchanun/bcp@^0.1.1"
   }
 }
 ```
@@ -201,31 +203,33 @@ Only after `npm run rc:check` passes and `CHANGELOG.md` is ready:
 
 ```bash
 git status
-git tag -a v0.1.0 -m "BCP Framework v0.1.0"
-git push origin v0.1.0
+git tag -a v0.1.1 -m "BCP Framework v0.1.1"
+git push origin v0.1.1
 ```
 
 Use the actual version from `package.json` in the tag.
 
 The GitHub Release Check workflow validates a `v*` tag, rechecks the npm target version, and uploads the npm tarballs as workflow artifacts. It does not publish them.
 
-## 9. Guarded first publish
+## 9. Guarded publish
 
 After the tag workflow artifacts have been reviewed, publish from an authenticated local npm session with:
 
 ```bash
-npm run release:publish -- --yes
+npm run release:publish:yes
 ```
 
+This explicit script is preferred over forwarding `--yes` through `npm run`, because npm CLI argument forwarding can vary by npm/platform version.
+
 The command refuses to publish unless all of these conditions are true:
 
-- `--yes` is supplied
+- explicit publish confirmation is present
 - the git working tree is clean
 - HEAD has the exact tag `v<package-version>`
 - npm authentication succeeds
 - the RC checks succeed again
 - staged package names and versions match the selected release
-- the target version has not already been published
+- the target version has not already been accepted by npm
 
 For `0.x` releases the default npm dist-tag is:
 
@@ -242,27 +246,29 @@ latest
 Override the tag explicitly when needed:
 
 ```bash
-BCP_DIST_TAG=beta npm run release:publish -- --yes
+BCP_DIST_TAG=beta npm run release:publish:yes
 ```
 
 PowerShell example:
 
 ```powershell
 $env:BCP_DIST_TAG="beta"
-npm run release:publish -- --yes
+npm run release:publish:yes
 ```
 
-The framework publishes first. `create-bcp-app` publishes only after the framework publish succeeds and npm confirms that version is visible in the registry.
+The framework publishes first. After `npm publish` succeeds, the release script accepts either normal version visibility or the selected dist-tag pointing at the new version. This prevents npm registry/security-processing delays from being misclassified as a failed publish.
 
 ## 10. Recover from a partial publish
 
-If the framework package was published successfully but publishing `create-bcp-app` failed, fix the external issue without changing the release commit or tag, then use:
+If the framework package was accepted by npm but publishing `create-bcp-app` failed, fix the external issue without changing that release commit or tag, then use:
 
 ```bash
-npm run release:publish -- --yes --resume
+npm run release:resume
 ```
 
-`--resume` skips versions that already exist and attempts only the missing package. Do not use `--resume` to overwrite or replace an existing npm version; npm versions are immutable.
+Resume mode intentionally does not run `release:version-check` or `npm publish --dry-run` for the already-published version. It still runs the complete local release checks and package smoke tests, verifies package ownership, skips package versions already accepted by npm, and attempts only the missing package.
+
+Do not use resume mode to overwrite or replace an existing npm version; npm versions are immutable.
 
 ## 11. Install the preview release
 
@@ -288,11 +294,11 @@ import {
 
 The scoped package can also be installed directly as `@chidchanun/bcp@next`, but applications using the framework's documented `bcp` import path should prefer the alias form above.
 
-## 12. Trusted publishing after the initial release
+## 12. Trusted publishing
 
 For subsequent releases, prefer npm Trusted Publishing with GitHub Actions instead of a long-lived write token. npm supports GitHub Actions OIDC publishing and recommends trusted publishing for CI-based releases.
 
-The first package version must exist before its npm package settings can be configured for a trusted publisher. After the initial manual release, configure the repository/workflow as a trusted publisher on npm and move the real publish action into the guarded GitHub release workflow.
+After the npm package settings are available, configure the repository/workflow as a trusted publisher and move the real publish action into the guarded GitHub release workflow.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chidchanun/bcp",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "BCP Framework - a React full-stack framework with file-based routing, SSR, APIs, middleware, islands, caching and standalone production builds.",
   "type": "module",
   "license": "MIT",
@@ -24,7 +24,7 @@
     "node": ">=24.11.0"
   },
   "bin": {
-    "bcp": "./packages/cli/bin/bcp.mjs"
+    "bcp": "packages/cli/bin/bcp.mjs"
   },
   "exports": {
     ".": {

package/packages/client/src/index.tsx

@@ -1,14 +1,17 @@
 import "./persistent-layout-runtime.js";
 
 export {
-    Link,
     navigate,
     useRouter,
-    type LinkProps,
     type NavigationOptions,
     type Router,
 } from "./router-v2.js";
 
+export {
+    Link,
+    type LinkProps,
+} from "./link.js";
+
 export {
     useNavigation,
     type NavigationState,

package/packages/client/src/link.ts

@@ -0,0 +1,123 @@
+import {
+    createElement,
+    type MouseEvent,
+} from "react";
+
+import {
+    navigate,
+    useRouter,
+    type LinkProps,
+} from "./router-v2.js";
+
+export type {
+    LinkProps,
+} from "./router-v2.js";
+
+export function Link({
+    href,
+    replace = false,
+    scroll = true,
+    onClick,
+    ...props
+}: LinkProps) {
+    useRouter();
+
+    function handleClick(
+        event: MouseEvent<HTMLAnchorElement>
+    ) {
+        onClick?.(event);
+
+        if (
+            event.defaultPrevented ||
+            !shouldInterceptClick(
+                event
+            )
+        ) {
+            return;
+        }
+
+        event.preventDefault();
+
+        void navigate(
+            href,
+            {
+                replace,
+                scroll,
+            }
+        ).catch(
+            (error) => {
+                if (isAbortError(error)) {
+                    return;
+                }
+
+                console.error(
+                    "[BCP Router] navigation failed:",
+                    error
+                );
+                window.location.assign(
+                    href
+                );
+            }
+        );
+    }
+
+    return createElement(
+        "a",
+        {
+            ...props,
+            href,
+            onClick:
+                handleClick,
+        }
+    );
+}
+
+function shouldInterceptClick(
+    event: MouseEvent<HTMLAnchorElement>
+): boolean {
+    if (
+        event.defaultPrevented ||
+        event.button !== 0 ||
+        event.metaKey ||
+        event.ctrlKey ||
+        event.shiftKey ||
+        event.altKey
+    ) {
+        return false;
+    }
+
+    const anchor =
+        event.currentTarget;
+
+    if (
+        anchor.target &&
+        anchor.target !== "_self"
+    ) {
+        return false;
+    }
+
+    if (
+        anchor.hasAttribute(
+            "download"
+        )
+    ) {
+        return false;
+    }
+
+    return (
+        new URL(
+            anchor.href,
+            window.location.href
+        ).origin ===
+        window.location.origin
+    );
+}
+
+function isAbortError(
+    error: unknown
+): boolean {
+    return (
+        error instanceof DOMException &&
+        error.name === "AbortError"
+    );
+}

package/packages/client/src/router.tsx

@@ -1 +1,11 @@
-export * from "./router-v2.js";
+export {
+    navigate,
+    useRouter,
+    type NavigationOptions,
+    type Router,
+} from "./router-v2.js";
+
+export {
+    Link,
+    type LinkProps,
+} from "./link.js";