@inkandswitch/patchwork-pkg-base 0.0.0 → 0.0.2

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@inkandswitch/patchwork-pkg-base",
-  "version": "0.0.0",
+  "version": "0.0.2",
   "type": "module",
   "description": "Base packages for the Patchwork system",
-  "files": [
-    "static-dist"
-  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/inkandswitch/patchwork-pkg-base.git"
+  },
   "scripts": {
     "build:static": "node scripts/build-static.mjs",
     "build:static:fresh": "node scripts/build-static.mjs --build",
@@ -15,5 +16,6 @@
     "dev:tools": "pnpm build:static && pnpm serve:tools",
     "dev": "node scripts/serve-tools.mjs --port 2121",
     "deploy:tools": "pnpm build:static && pnpm dlx netlify-cli deploy --dir=static-dist --prod"
-  }
-}
+  },
+  "packageManager": "pnpm@11.15.1"
+}

package/README.md

@@ -1,153 +0,0 @@
-# patchwork-base
-
-A collection of the core tools that comprise the Patchwork system.
-
-## Engineering Notes
-
-Tools in this collection should be reliable and maintained: these are the core tools, after all.
-
-Within a given distribution, it is reasonable to assume these tools exist, however tools in this collection should never assume the existence of other tools.
-
-Regardless, these tools should not depend on each other's implementations or their internal structure.
-
-Each directory in this collection can be built completely independently. Tools do not share lockfiles, node modules, or even necessarily build systems or web frameworks.
-
-Please be careful not to violate these isolation principles.
-
-## Dependencies
-
-- External deps (`@inkandswitch/patchwork-*`, `solid-js`, etc.) are pinned to
-  normal published npm versions.
-
-## Caveat
-
-- A few tools depend on sibling tools in this repo
-  (`codemirror-markdown` → `codemirror-base`, `tenfold` → `codemirror-base` and
-  `codemirror-markdown`, `account-picker` → `contact`). Those are referenced as
-  `link:../<sibling>` in the sibling's `package.json`, which creates a live
-  symlink into `node_modules`. Building the sibling is enough — no publish
-  step, no `workspace:*` protocol.
-
-## Building one tool
-
-```sh
-cd history-view
-pnpm install
-pnpm build
-```
-
-For tools that `link:` to a sibling, build the sibling first so its `dist/`
-exists (e.g. `codemirror-base` before `tenfold`). Running `pnpm -r build` at
-the root happens to go in alphabetical order, which puts dependencies ahead of
-dependents for the current set of links.
-
-## Building everything
-
-From the repo root:
-
-```sh
-pnpm install   # install in every tool
-pnpm build     # build every tool that has a build script
-```
-
-There is no root workspace — these just run `pnpm` recursively over each tool
-directory. The filter (`--filter './*' --filter '!./static-dist/**'`) excludes
-the `static-dist/` output folder, so they're safe to run even when a previous
-bundle is still present. (A bare `pnpm -r build` would instead try to "build"
-the copied bundles under `static-dist/packages/*` and fail, since those have no
-`node_modules`.) Because `install` is a real script, plain `pnpm install` at the
-root installs all the tools too.
-
-## Static-HTTP deployment (shell + tools bundle)
-
-The tools can be deployed as a static HTTP bundle and loaded by any Patchwork
-**shell** (the boot runtime). The two halves are independent:
-
-- **Tools bundle** (lives here) — `static-dist/` (`modules.json` +
-  `packages/<tool>/dist/…`), produced by `scripts/bundle.mjs`. Deployed to
-  Netlify (the repo is private, so GitHub Pages would need a paid plan).
-  `bundle` also writes a `_headers` file granting
-  `Access-Control-Allow-Origin: *`, which Netlify (and Cloudflare Pages) honour
-  so a shell can load these tools cross-origin.
-- **Shell** (lives in `patchwork-next`) — there is no separate shell in this
-  repo. Any patchwork-next site is a shell; `sites/tiny-patchwork` is the
-  canonical one (PWA-ready). The static-manifest support lives in the bootloader
-  (`ModuleWatcher` / `SiteConfig.defaultModules`), so a shell just needs to point
-  its `defaultModules` at a tools host.
-
-A shell can point at any tools host via `PATCHWORK_SYSTEM_PACKAGE_LIST_URL` (build time) or
-`localStorage.systemPackageListURL` (runtime), so the same deployed shell can run
-against an `automerge:` module-settings doc, this static tools bundle, a PR
-preview, or a local tools server — no shell rebuild needed for the runtime
-override.
-
-### Build / serve / deploy the tools bundle
-
-```sh
-pnpm install          # install every tool (skips static-dist/)
-pnpm build            # build every tool (skips static-dist/)
-pnpm bundle           # aggregate built tool dist/ -> static-dist/ + modules.json
-
-pnpm serve:tools      # serve static-dist/ on :4455 with CORS (local tools host)
-pnpm dev:tools        # bundle + serve:tools
-
-pnpm deploy:tools     # bundle + netlify deploy --prod (static-dist/)
-```
-
-A clean bundle from scratch is `pnpm install && pnpm build && pnpm bundle`
-(which is exactly what Netlify runs).
-
-`modules.json` uses relative `./packages/…` URLs that resolve against the
-manifest's own URL, so the bundle works at any host or base path.
-
-The first `pnpm deploy:tools` will prompt you to log in and link/create a
-Netlify site (`netlify.toml` sets the publish dir). After that it's one command.
-
-### Continuous deploy + PR previews (Netlify Git integration)
-
-Our production deployment goes to Netlify, so we have included a `netlify.toml` for
-convenience.
-
-To aid in branch review, we have configured deploy previews on the GitHub repo.
-The preview is of the _tools bundle_, so to test a PR's tools in any shell,
-point it at the preview's manifest — no shell rebuild needed:
-
-```js
-localStorage.systemPackageListURL =
-  "https://deploy-preview-123--<site>.netlify.app/modules.json";
-```
-
-### Run a shell against a local tools bundle
-
-Local development can deploy as usual via pushwork, but to test the build process
-you can always run a local webserver to host the JS and point your local shell at it.
-
-```sh
-# terminal 1 — tools host (in patchwork-base)
-pnpm dev:tools
-
-# terminal 2 — shell (in patchwork-next)
-PATCHWORK_SYSTEM_PACKAGE_LIST_URL=http://localhost:4455/modules.json \
-  pnpm --filter tiny-patchwork dev
-```
-
-At runtime you can also point an already-running/deployed shell at a tools host
-without a rebuild:
-
-```js
-localStorage.systemPackageListURL = "http://localhost:4455/modules.json";
-```
-
-## Installing modules
-
-To build a full set of modules for automerge-backed live development, run the usual install/build on all of them first. Once the tools are built, you can push each one to a module settings document using the following commands>
-
-Right now this is a bit janky, but once you have the pushwork and the patchwork-modules CLI tool installed, you should be able to run:
-
-```sh
-export MODULE_SETTINGS_DOC_URL=`pw-modules init`
-pnpm -r exec pushwork init
-pnpm -r register
-```
-
-Of course, if you already have a patchwork modules document, you can supply it.

package/static-dist/packages/doc-openwith/.pushwork/config.json

@@ -1,9 +0,0 @@
-{
-  "version": 4,
-  "rootUrl": "automerge:egLXA9YDV1y53RpLa3vQn1hA3bb",
-  "backend": "subduction",
-  "shape": "vfs",
-  "artifactDirectories": [
-    "dist"
-  ]
-}

package/static-dist/packages/doc-openwith/.pushwork/storage/st/orage-adapter-id

@@ -1 +0,0 @@
-2c93876d-fd8f-46df-83b5-b8be2a8f4cb6

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/blobs/6b9ea156778646078da7fbc4c15de0f900000000000000000000000000000000/aa3b2b19c2ca8dde37ceb1d002d6eca312183fe8dc4eb69f97e274fedce82aa1

@@ -1,2 +0,0 @@
-�oJ��;+�%M�J�@���$�V|-
-~��N�A�u�3tq��s8�kx9��{�z�n��.!����s��K�+��s쟳�X���
�U��P�I���o
�`�`nʽ�=R�8�<9l���0��s�y�4/����}�d����;s�Də,���^#�<CZ�W�h

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/blobs/a49a894173564c34bd87cfe6e51e38c600000000000000000000000000000000/ce0555adaac1e943e83c019624fd631c917160d12ac7d92a371c815951380357

@@ -1,5 +0,0 @@
-�oJ��U���R]HQ�s�[�Ų�%J�¶
-C��D����&Ei��΅ �0E��]��U�?t��`�4�,2�@�$ȇ�:���{�C߹����oνh۔6�RѴj��Ժk�{wpGYY�f�|BV���=�R�۳%N���]�����.���˫�ޘ$E��uXʓRM��&��iUS��-�b
-��5��x����0E��(`���%���Os<�!W��|L
A(‚H
�6!&̧%�@�:k�2�Y�ҏ=�xaŏ�J�����Lw_����8�CVúS3�>��4�.>��0�����+48f�}!���Z?Gנ6�wit�wkd�F�^
-�&�B���
-S��WHx�ߙ��3�

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/0323ab06f8db48fd9116cff9ab101e6c00000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/0c4c3d4c3ae045298fe72640132a206a00000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/1f9e1128e0a34b47a0865cd1ed2ca42800000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/2ea119536552427ab3fbf3946645596000000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/6b9ea156778646078da7fbc4c15de0f900000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/9028cd12a03f456c932c32b0d1ba73fb00000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/a49a894173564c34bd87cfe6e51e38c600000000000000000000000000000000

@@ -1 +0,0 @@
-

package/static-dist/packages/doc-openwith/.pushwork/storage/su/bduction/ids/bc05fcf497064ceb990692bd74311a5200000000000000000000000000000000

@@ -1 +0,0 @@
-