Skip to content

Conversation

@cincodenada
Copy link

This is actually the package version that matters here, and with @jest/core's package.json it's quite possible to have e.g. [email protected] but @jest/[email protected], so referencing the jest version will not always give you the correct answer.

I know this because this is exactly the situation I'm in:

› npm ls @jest/reporters
[snip]
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ @jest/[email protected]
      └── @jest/[email protected]

So, I initially tried to use summary_reporters and got an error, even though I'm on [email protected], because I have @jest/[email protected]

This is actually the package version that matters here, and with `@jest/core`'s `package.json` it's quite possible to have e.g. `[email protected]` but `@jest/[email protected]`, so referencing the `jest` version will not always give you the correct answer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant