boxpositron/envsitter-guard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: depend on the published envsitter 0.1.0
CI / Test (Node 22) (push) Has been skipped
Details
CI / Test (Node 26) (push) Has been skipped
Details
CI / Test (Node 24) (push) Has been skipped
Details
CI / E2E (OpenCode 1.18.31 + 2.0.32) (push) Has been skipped
Details
CI / E2E (OpenCode 1.19.3 + 2.1.0) (push) Has been skipped
Details

Browse Source 
Refresh package-lock.json so npm ci resolves envsitter 0.1.0 from the registry (integrity matches the published tarball), which fixes CI's ETARGET failure.
This commit is contained in:
David Ibia
2026-10-21 00:10:18 +01:00
parent 5325e83ac1
commit 7c8e1251a3
2 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+1 -1
View File
@@ -51,7 +51,7 @@ Tests use Node’s built-in test runner, compiled via `tsc` into `dist-test/`.
- Cross-version e2e (needs the CLIs installed; not part of `npm test`): `npm run test:e2e`
- Run a single test file:
- `npm run build:test && node --test dist-test/test/envsitter-guard.v2.test.js`
- Until `envsitter` 0.1.0 is published, tests need a local build: `npm pack` in `../envsitter`, then `npm install --no-save <tarball>` here.
- To test against an unreleased `envsitter`: `npm pack` in `../envsitter`, then `npm install --no-save <tarball>` here (CI always uses the published version from the lockfile).
Pre-commit checks are enforced via Husky:
- `npm install` installs the git hook.