mdn / mdn/webextensions-examples

Remove example extensions that depend on npm

Open
#398 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

example idle needs info on hold
Dominant language
JavaScript
Stars
4.5k
Forks
2.6k
Avg merge
15h 27m
Merged PRs (30d)
3

Description

Several of the examples here pull in dependencies for stuff like react, babel, webpack, eslint. They are useful to show how WebExtensions can integrate these technologies, but I think they are outside the core scope of this repo, which is to show how to use the WebExtension APIs.

They are still useful and if they were zero-cost, then I'd be happy to keep them, but they are a significantly greater maintenance burden than extensions that just use the WebExtension APIs. So I'd propose we just remove these examples.

This applies to:

Contributor guide

Open the 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.

Research direction

Start by reviewing the five named example directories: eslint-example, mocha-client-tests, react-es6-popup, store-collected-images, and webpack-modules. Confirm their npm-dependent contents and remove the examples so the repository retains only examples focused on the WebExtension APIs.

Written by the indexing model from the issue text.

Assessment

Tech stack
babel, eslint, javascript, react, webpack
Domain
frontend
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.