Clean up multiple, redundant dependencies in yarn.lock #1180
Comments
Merged
toolness
added a commit
that referenced
this issue
Apr 12, 2020
This fixes #300 by using node-sass-chokidar. I'm not a big fan of what this is doing to our `yarn.lock`, as it seems to have brought in yet another version of chokidar and a few other dependencies we already have, but since it's all on the build side and not in the browser I think it's ok. Still, we should figure out if there's an easy way to clean up the `yarn.lock` at some point, so I've filed #1180 to address it later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of #1179 we now have 3 versions of chokidar in our
yarn.lock, at two of which differ only in patch version.I've heard this kind of thing can be cleaned up by uninstalling and then reinstalling the relevant packages, but I've never actually tried it. It would also be nice if there were a tool that just did all this deduping automatically, although yarn does seem to dedupe if everything is installed at once, so yet another option may be to just delete our
yarn.lockand regenerate it from scratch, and test rigorously to make sure nothing's broken.The text was updated successfully, but these errors were encountered: