Upgrade Node to 20 (devbridge-autocomplete requires node >= 20)

Open
#4,430 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ansible, node.js

Research direction

Start with .nvmrc (pinned to 18.20.3) and the devbridge-autocomplete engine requirement in package.json, then run yarn install under Node 20 to confirm the error goes away. Check bin/update, where system('bin/yarn') ignores failures, and the CircleCI config and Ansible production setup for Node versions. Done means yarn install, the esbuild build and bin/update on a fresh worktree all pass, and CI is green.

Written by the indexing model from the issue text.

Description

yarn install fails on a clean setup:

error [email protected]: The engine "node" is incompatible with this module. Expected version ">=20". Got "18.20.3"

.nvmrc pins 18.20.3, while package.json requires devbridge-autocomplete ^2.0.1, which declares engines.node >= 20. bin/update runs system('bin/yarn') without failing on error, so the problem goes unnoticed and dependencies may be left stale.

Tasks:

  • Bump .nvmrc to Node 20 LTS and check that yarn install and the esbuild build pass.
  • Check whether NODE_OPTIONS=--openssl-legacy-provider is still needed on Node 20.
  • Align the CircleCI Node image and production (Ansible) with the new version.
  • Consider using system! for bin/yarn in bin/update so it fails loudly.

Acceptance: bin/update on a fresh worktree finishes with no yarn errors, and CI is green.

🤖 Generated with Claude Code

Dominant language
Ruby
Stars
79
Forks
31
Avg merge
2d 1h
Merged PRs (30d)
23

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PopulateTools/gobierto

All issues in PopulateTools/gobierto

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.