Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update to node 18

Open
#202 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js

Research direction

No file or test is named. Start by locating the repository's Node version and dependency configuration, then check how node-sass constrains the upgrade. Done means the project targets Node 18 and its dependencies can be updated without breaking the client.

Written by the indexing model from the issue text.

Description

Some of our dependencies (node-sass in particular) no longer support node versions lower than 18. Let's update node so we can update dependencies.

Dominant language
JavaScript
Stars
11
Forks
14
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 mozilla/bugzy

All issues in mozilla/bugzy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.