loading...

Discussion on: What problems do front end developers face currently that do not have a well formed solution?

Collapse
evanroggenkamp profile image
Evan Roggenkamp

This is the biggest reason I’ve steered clear of NPM. The whole thing feels like this huge insurmountable monolith.

Collapse
jwp profile image
John Peters

And even if it's tamed, who knows what's in the cage? There are so many things in the node_module folder it's painful to scroll from top to bottom much less know wtf they do.

Thread Thread
techranga profile image
Shreenath Ranganathan Author

I may sound like a newbie here, and correct me if I'm wrong, but can we not exercise some amount of control over what is there in node_modules? I've used 'create react-app' only once, post which I've just gone with 'npm init' and inject dependencies as needed along the way. Every time I inject them, I make it a point to go through what stuff have been added and read through why they are needed since the documentation for these are always available.

Maybe I'm just being tedious there haha! Just a habit.

Thread Thread
jwp profile image
John Peters

Hello Shreenath;

For me I have different perspectives based on the many different platforms I worked over the years. I worked 7 years on the IBM ISeries, where upgrades to the entire operating system well almost always 100% flawless. The I worked in Java for 10 years where once again upgrades were flawless. Then I moved to .NET were again, upgrades were flawless. The content in all of those systems was well defined and guaranteed Not has dependency issues.

This is the opposite with NPM which we are taught to use in Angular, React, and Vue. Its easy to spend an entire week doing just an upgrade. All I'm saying is that the NPM dependency ecosystem is a bad experience. It's nowhere close to being a good product.