Skip to content

Fix lint tooling and move publishing to Node 22 - #137

Open
rcosta358 wants to merge 1 commit into
mainfrom
codex/issue-124-lint-node22
Open

rcosta358 wants to merge 1 commit into
mainfrom
codex/issue-124-lint-node22

Conversation

@rcosta358

Copy link
Copy Markdown
Collaborator

Closes #124.

Update ESLint, remove obsolete test scripts and unused tooling, and move publishing to Node 22. Fix existing semicolon violations.

Validated on Node 22: dependency install, lint, type checking, production build, and extension installation.

Generated by Codex.

@CatarinaGamboa CatarinaGamboa left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small thing for #124's Node 22 move, outside this diff:

.devcontainer/devcontainer.json still uses mcr.microsoft.com/devcontainers/javascript-node:20. The point of the move is that the Vitest and @vscode/test-electron versions added later in this stack need Node 22, so anyone working in the devcontainer will hit that once #140 / #144 land, while CI on 22 passes. Suggest bumping the image to javascript-node:22, and optionally adding "engines": { "node": ">=22" } to client/package.json.

Reviewed with Claude Code (reviewer + adversarial agents per PR, findings checked against the code before posting).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing Testing related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix lint tooling and move to Node 22

2 participants