Closed frandiox closed 5 years ago
Made this change locally to test and it's all working now - thanks!
@chrisgundersen For the next time, you can try yarn why <package-name>
or npm ls <package-name>
and it will tell you what dependencies are requiring the package 👍
Thanks! I managed to fix this just now with a yarn upgrade
.
Hi! The only dependency affected was
npm-run-all
. Fixes #112