[Bug]: Dependency with outdated Windows executables about jest HOT 4 CLOSED

The link you provided is pointing to a dev dependency. This is not Jest dependency, so it is incorrect to say that "Jest depends on node-notifier".

In this case node-notifier is simply used for testing the code base. More precisely, the node-notifier package is used to test the notify configuration option.

from jest.

Totally understood that it's not a runtime dependency, and that we're into semantics where I would consider any runtime, test, dev dependencies to all be dependencies [especially if they have any opportunity to affect the contents of the release bytes].

All good if this isn't a concern for Jest, I'm not here to push for any change that isn't wanted :)

from jest.

Yeah, we don't ship it (it's an optional peer (

Also, assuming since we don't have it as a dep ourselves it's fine, would it have been an issue? I really don't know how these things work 😅

from jest.

With much embarrassment, I think at this stage this is a case of my inexperience with npm (I've more of a Maven background) and not identifying that I was looking at an older version of Jest in the dependency tree prior to your moving to peerDependencies. I think you've already fixed this in the later versions :/

[I think this can be closed, but leaving open so a Jest maintainer can have closure and, y'know, call me a fool etc :) ]

from jest.