Skip to content

fix: run full n8n-node lint in CI#5

Merged
OndrejDrapalik merged 1 commit into
mainfrom
fix/pnpm-workspace-lint
Jul 8, 2026
Merged

fix: run full n8n-node lint in CI#5
OndrejDrapalik merged 1 commit into
mainfrom
fix/pnpm-workspace-lint

Conversation

@OndrejDrapalik

@OndrejDrapalik OndrejDrapalik commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • pnpm-workspace.yaml had no packages: field, so pnpm 11 (pinned via packageManager) errored packages field missing or empty whenever n8n-node lint shelled out to pnpm — pnpm lint was unrunnable.
  • CI hid this by running pnpm lint:basic (plain eslint) instead of the full pnpm lint (n8n-node lint).
  • Fix: declare the single package (packages: [.]) and switch the CI lint step to pnpm lint.

Unblocks n8n community-node verification, which expects the full n8n-node lint to pass.

Test plan

  • pnpm install --frozen-lockfile — clean, no lockfile drift
  • pnpm lint — exits 0 (previously ERROR packages field missing or empty)
  • pnpm typecheck — exits 0
  • CI "Lint and typecheck" job green on this PR

pnpm-workspace.yaml declared no packages field, so pnpm 11 errored
"packages field missing or empty" whenever n8n-node lint shelled out
to pnpm — making `pnpm lint` unrunnable. CI masked this by running
`pnpm lint:basic` (plain eslint) instead of the full `pnpm lint`.

- Add `packages: [.]` to pnpm-workspace.yaml so n8n-node lint runs.
- Switch CI lint step from `pnpm lint:basic` to `pnpm lint`.

Verified: pnpm install --frozen-lockfile, pnpm lint, pnpm typecheck all
pass (lint was previously erroring). Unblocks n8n community-node
verification, which expects the full lint to pass.
@OndrejDrapalik OndrejDrapalik merged commit 1f489d0 into main Jul 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants