Honestly, this feels like the correct behavior to me. The dependencies of another package are an implementation detail and if they change, your project could break.
Not arguing that at all - I'm totally onboard with it. The whole family of dependencies needs to be there (and locked to a version) for things to work repeatably. I just needed some disk space back. As long as you don't mind running yarn or npm install when you come back to working on a given project, this seems to be a perfectly functional way of working to me.
Edit: Just realized you weren't replying directly to my post! Ha - well, seems we may be on the same page anyway. 🍳
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Honestly, this feels like the correct behavior to me. The dependencies of another package are an implementation detail and if they change, your project could break.
Not arguing that at all - I'm totally onboard with it. The whole family of dependencies needs to be there (and locked to a version) for things to work repeatably. I just needed some disk space back. As long as you don't mind running
yarn
ornpm install
when you come back to working on a given project, this seems to be a perfectly functional way of working to me.Edit: Just realized you weren't replying directly to my post! Ha - well, seems we may be on the same page anyway. 🍳