Skip to content

Having @types/node in dependency causes unexpected upstream issues. #229

@Gijsdeman

Description

@Gijsdeman

A concrete example:

jest-config@30.2.0:
peerDependencies:
  '@types/node': '*'

Thus, when having @playform/pipe as (indirect) dependency, a mismatch in @types/node can occur. Moving the dependency to peer dependencies resolves this conflict while still indicating that this version of @types/node must be installed.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions