Find the package.json lines that stop vsce before you run the release build
189
Find the package.json lines that stop vsce before you run the release build
docker run --rm -v "$PWD":/work getreadystack/vsix-publish-lint /work/file
The same 16 rules as the VS Code extension, in a container. Mount a folder on /work.
--rules lists every ruledocker run --rm -e READYSTACK_LICENSE=<key> -v "$PWD":/work getreadystack/vsix-publish-lint --dir /work --ci
One hour of specialised freelance developer time runs $75-$150 on Upwork's own 2026 rate guide; a rejected publish usually costs more than one.
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "vsix-publish-lint": { "command": "npx", "args": ["-y", "@readystack/vsix-publish-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence; the full sweep is free for 7 days). The agent gets every finding with the line number.
- name: VSIX Publish Lint
run: npx -y @readystack/vsix-publish-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/vsix-publish-lint --dir /work --ci)
Try the full run free for 7 days — no key needed. Then one licence, 7-day refund, no questions. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Content type
Image
Digest
sha256:e3939485c…
Size
46.1 MB
Last updated
about 6 hours ago
docker pull getreadystack/vsix-publish-lint