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

Firefox build discouraged?

Open
#28 0 comments 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

Research direction

Start by reviewing the Firefox extension build process and the npm install --global web-ext command shown in the report. Determine whether the deprecation warnings affect building or only the tooling dependencies; done means documenting a supported Firefox build path or identifying a reproducible build failure.

Written by the indexing model from the issue text.

Description

Hi
Thanks for your tool. I work with Firefox and tried to build the extension. I get the following result:

npm install --global web-ext

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead

npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead

npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.

This looks not very encouraging.
Are there other ways to build the extension or is it doomed for Firefox?
Thanks for your help!
cheers

Dominant language
JavaScript
Stars
421
Forks
27
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 beyondcode/livewire-devtools

All issues in beyondcode/livewire-devtools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.