Skip to content
This repository has been archived by the owner on Aug 22, 2023. It is now read-only.

@oclif/errors should be a dependency #83

Closed
aparajita opened this issue Jul 10, 2019 · 2 comments · Fixed by #90
Closed

@oclif/errors should be a dependency #83

aparajita opened this issue Jul 10, 2019 · 2 comments · Fixed by #90

Comments

@aparajita
Copy link

See this line:

import {CLIError, error, exit, warn} from '@oclif/errors'

@oclif/errors must be declared as a dependency, not a devDependency. The only reason you aren't getting bitten by this (mostly) is because the current implementation of npm and yarn are shamelessly flattening the package hierarchy, thus hiding missing dependency declarations.

@HosseinAgha
Copy link

HosseinAgha commented Oct 30, 2019

I encountered this error when using Apollo CLI and yarn pnp. The problem is that your package relies on a none standard behaviour for dependency resolution.
Pinging @arcanis As suggested in pnp troubleshooting page.

@arcanis
Copy link

arcanis commented Oct 30, 2019

Related: oclif/oclif#150

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants