Replies: 2 comments 1 reply
-
As this rule requires a You can manage dependencies in a
If you do take this route, you loose Bit's automated "workspace" management for dependencies, where if different components require different versions of the same dependency, Bit automates Yarn workspaces or pnpm workspaces (and soon npm workspaces) behind the scenes for this to work seamlessly. |
Beta Was this translation helpful? Give feedback.
-
see also my comments here |
Beta Was this translation helpful? Give feedback.
-
I use
eslint-plugin-import
to verify packages I'm importing exist/are correct. It checkspackage.json
to see if a dependency exists. See this rule for details.However, because I'm installing dependencies with
bit install
, it means dependencies aren't populated inpackage.json
. Therefore I can't useeslint-plugin-import
. I don't want to disable it just so I can use Bit.Is there a way to get this to work with Bit?
Beta Was this translation helpful? Give feedback.
All reactions