@appshell/react 1.0.0-alpha.88 → 1.0.0-alpha.89

package/dist/types/config/src/index.d.ts

@@ -9,6 +9,8 @@ export type { Credential } from './credentials';
 export { default as generateManifest, manifestFrom } from './generate.manifest';
 export { loaderOf } from './loader';
 export { default as outdated } from './outdated';
+export { parsePackageName } from './package-name';
+export type { PackageName } from './package-name';
 export { activate, openOverlay, publish } from './publish';
 export type { OpenedOverlay, OverlayRemotePatch, PublishOptions, PublishResult } from './publish';
 export { default as sync } from './sync';

package/dist/types/config/src/package-name.d.ts

@@ -0,0 +1,20 @@
+/**
+ * An npm package name split into where it belongs and what it is called.
+ *
+ * `@acme/checkout` is scope `acme`, name `checkout`. A bare `checkout` declares no scope
+ * and belongs wherever the publisher does.
+ *
+ * One definition because three places used to strip the scope with their own copy of the
+ * same regular expression — the cli's `identify`, its workspace scan, and the webpack
+ * plugin. Three copies of a rule about identity is three chances for a package to publish
+ * to a different place than the tooling thinks it does.
+ *
+ * Scope is worth declaring for the reason it is worth checking in: `@acme/checkout` says
+ * where it belongs in a file under review, identically for everyone, rather than landing
+ * in whichever namespace the person running the publish happens to carry.
+ */
+export type PackageName = {
+    scopeId?: string;
+    name: string;
+};
+export declare const parsePackageName: (raw: string) => PackageName;

package/dist/types/config/src/publish.d.ts

@@ -2,6 +2,14 @@ import { AppshellManifest, Metadata, ModuleFederationLoader } from './types';
 export type PublishOptions = {
     registry: string;
     token?: string;
+    /**
+     * Where this package belongs, when the package name declares it.
+     *
+     * Omitted means the publisher's own namespace, which is how every publish worked before
+     * this existed. The registry refuses a scope the caller does not own, so declaring one
+     * is a statement of fact rather than a request.
+     */
+    scopeId?: string;
     name: string;
     version: string;
     manifest: AppshellManifest;
@@ -11,7 +19,7 @@ export type PublishOptions = {
     force?: boolean;
 };
 export type PublishResult = {
-    /** `scope/name@version`. The scope comes from the token, not the caller. */
+    /** `scope/name@version`. From the package name where it declares one, else the token. */
     id: string;
     created: boolean;
     /** Empty unless a shared block was sent. See `openOverlay`. */
@@ -22,7 +30,7 @@ export type PublishResult = {
  * under a version that already exists is rejected by the registry, unless
  * `force` is set and the registry is configured to honor it (dev registries).
  */
-export declare const publish: ({ registry, token, name, version, manifest, visibility, metadata, force, }: PublishOptions) => Promise<PublishResult>;
+export declare const publish: ({ registry, token, scopeId, name, version, manifest, visibility, metadata, force, }: PublishOptions) => Promise<PublishResult>;
 /**
  * Activating a newer version of an already active package upgrades it in place.
  * @param application `scope/name`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appshell/react",
-  "version": "1.0.0-alpha.88",
+  "version": "1.0.0-alpha.89",
   "description": "React utilities for building micro-frontends with Appshell and Module Federation",
   "main": "dist/main.js",
   "types": "dist/types/react/src/index.d.ts",
@@ -34,8 +34,8 @@
     "react": "^18.2.0",
     "react-dom": "^18.2.0"
   },
-  "gitHead": "cd4b3e29225192856a96df47661031e65928f322",
+  "gitHead": "e2b69e42e63fc753f4d400ef957dcc233223fcee",
   "dependencies": {
-    "@appshell/runtime": "^1.0.0-alpha.88"
+    "@appshell/runtime": "^1.0.0-alpha.89"
   }
 }