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

graceful-fs@2 and @3 support will be removed soon

Open
#86 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs
Domain
tooling

Research direction

Start by checking debowerify's dependency tree for graceful-fs@2 or @3 and reproduce the require behavior described in the issue. Confirm whether runtime dependencies use those versions; done means debowerify no longer depends on an affected version or the compatibility impact is otherwise resolved.

Written by the indexing model from the issue text.

Description

Hi. debowerify is currently #69 in my list of modules that would likely be broken when https://github.com/nodejs/node/pull/6413 lands (which is anticipated to happen before v7.0).

Note that graceful-fs@1 and graceful-fs@4 are ok and would not be broken by this, but a require() on graceful-fs@2 or graceful-fs@3 would cause an error soon.

That is, runtime warning fs: re-evaluating native module sources is not supported. would be turned into a throw.

If you or your deps use graceful-fs@2 or graceful-fs@3 in runtime — you are affected.

Tracking: https://github.com/nodejs/node/issues/5213.

Dominant language
JavaScript
Stars
491
Forks
49
PR merge metrics
No merged PRs in 30d

Getting set up

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 eugeneware/debowerify

All issues in eugeneware/debowerify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.