@wojciechpiskorz/astroix 0.0.16 → 0.0.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +1 -1
  2. package/dist/chrome.js +86 -82
  3. package/dist/index.js +238 -9
  4. package/dist/index.js.map +1 -1
  5. package/package.json +3 -2
package/README.md CHANGED
@@ -35,7 +35,7 @@ bun run build # tsup (node) + vite (chrome bundle) → dist
35
35
 
36
36
  ### Dogfood loop
37
37
 
38
- The e2e fixture consumes the local package via `file:../..` and registers `astroix()` in its `astro.config.mjs`. With both packages installed, run `bun run dev` (tsup watch) at the root in one terminal and `bun run dev` in `e2e/fixture/` in the other — the fixture dev server on `http://localhost:4312` runs the integration straight from your checkout.
38
+ The e2e fixture consumes the local package through `.astroix-local/` — a gitignored staging dir holding only the publish surface (`dist`, `package.json`, `README`, `LICENSE`), linked as `file:../../.astroix-local` (#123: a `file:` link to the repo root copies the whole checkout, nesting `node_modules` recursively). `bun run prepare-local` (run automatically before the fixture dev server boots) rebuilds `dist` when stale, re-syncs the staging dir, and refreshes the installed copy — so `bun run dev` in `e2e/fixture/` always serves the current build. A root `bun run dev` (tsup watch) plus a fixture dev server still works for iteration; re-run the fixture's dev script (or `bun run prepare-local`) to pick up each fresh build.
39
39
 
40
40
  ### Ports
41
41