Skip to content

VS Code extension: regenerate package-lock.json so the 0.2.0 publish works - #112

Merged
sagnik11 merged 1 commit into
mainfrom
claude/focused-sagan-at64y1
Nov 17, 2026
Merged

sagnik11 merged 1 commit into
mainfrom
claude/focused-sagan-at64y1

Conversation

@sagnik11

@sagnik11 sagnik11 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

The publish run for the VS Code extension 0.2.0 (from #110) failed at npm ci with EINTEGRITY. This PR regenerates the extension's lockfile so it installs and packages.

What was wrong

Four lockfile entries named newer versions but carried the integrity hashes of older ones, which suggests versions were edited by hand without re-resolving:

Package Lockfile said Hash belongs to
tmp 0.2.6 0.2.5
qs 6.16.0 6.15.2
linkify-it 5.0.2 5.0.1
serialize-javascript 7.0.3 6.0.2

The same kind of edit left markdown-it at 15.0.3 under @vscode/vsce, whose range is ^14.1.0. That version needs linkify-it ^6.1.0, which was never installed, so vsce package failed with linkify_it.LinkifyIt is not a constructor even after fixing the hashes.

The other 503 entries' hashes matched the npm registry's metadata. Every resolved URL points at registry.npmjs.org, so the bad hashes could only make installs fail, not swap in other code.

Fix

Regenerated agent-support/vscode/package-lock.json from package.json with npm install --package-lock-only. Every entry is now npm's own resolution within the declared ranges. package.json is unchanged.

Testing

  • A clean npm ci passes, with every tarball checked against its hash.
  • tsc, eslint and the mocha tests (11) pass.
  • npm run package builds autter-vscode-0.2.0.vsix, which includes the new findings code.
  • npm audit --omit=dev: 0 vulnerabilities.

After merge, I'll dispatch the publish workflow on main (it publishes the package.json version, 0.2.0).


Generated by Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

….0 publish work

The publish workflow's `npm ci` failed with EINTEGRITY for tmp, qs,
linkify-it and serialize-javascript. Their lockfile entries named newer
versions (0.2.6, 6.16.0, 5.0.2, 7.0.3) but carried the integrity hashes of
older ones (0.2.5, 6.15.2, 5.0.1, 6.0.2): versions had been edited by
hand without re-resolving. The same kind of edit left markdown-it at
15.0.3 under @vscode/vsce, whose range is ^14.1.0 and whose own
linkify-it ^6.1.0 was never installed, so `vsce package` failed with
"linkify_it.LinkifyIt is not a constructor" even with the hashes fixed.
The other 503 entries' hashes matched the registry.

Regenerated from package.json with `npm install --package-lock-only`, so
every entry is npm's own resolution within the declared ranges. Verified
with a clean `npm ci` (every tarball checked against its hash), tsc,
eslint, the mocha tests, `npm run package` (autter-vscode-0.2.0.vsix),
and `npm audit --omit=dev` (0 vulnerabilities).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
@sagnik11
sagnik11 merged commit 3606045 into main Nov 17, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants