those were (and possibly still are) necessary for other dependencies

If that's the case, then they should have specified them as peerDependencies. npm nowadays installs peerDependencies automatically, so this shouldn't lead to missing dependencies, as long as they are specified correctly.

For example, the globals dependency was originally added (by you :-) in PR #10293.

WOW it's been a while :D Can't believe I was a contributor for 6 years!

Anyways, tracked the origins of each dependency listed.

caniuse-lite
- Where added: Add the caniuse-lite package #14612
- Why: In hope this will stop autoprefixer from complaining about out-of-date version of caniuse-lite. Not actually used directly.
eslint-plugin-html
- Where added: Update the eslint-plugin-mozilla to the latest version (PR 10905 follow-up) #11127
- Why: "This required adding a number of additional dependencies, based on [dead link]"
eslint-plugin-fetch-options
- Where added: Update the eslint-plugin-mozilla to the latest version (PR 10905 follow-up) #11127 (same as above)
- Why: "This required adding a number of additional dependencies, based on [dead link]"
globals
- Where added: Upgrade to Babel 7 #10293
- Why added: I think it was not actually needed at a time, might be still true.
jstransformer-nunjucks
- Where added: Replace Wintersmith with Metalsmith #18248
- Why: "necessary for Metalsmith to build the website"

Uh oh!

Extra dependencies? #18354

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions