Poll: I use npm, and the JavaScript I write runs...
-
-
If there are thing npm could do today to improve FE that are practical for our team of 18 engineers, I am all ears.
-
For me, a lot of what's tricky about FE tooling is the rough edges around introspecting node_modules.
-
For example, require.resolve gives you the main file, but it's not always in the root. These issues are ancient and wontfixed.
-
Maybe there's already a nice npm-maintained package floating around that gives you a graph of node_modules in consumable form?
-
Different in what way from the output of `npm ls --json`? File-level granularity instead of module-level?
-
Gotta break out my laptop and check :)
-
This might be a good enough primitive but I'd have to walk the FS again to find the entry points (this is focused on deps)
-
The peerMissing stuff in here is great! Hadn't noticed it.
- 1 more reply
New conversation -
-
-
For non-webpack users*** We should be okay regardless

-
Come on man. Every tool can find a way to support it.
-
That's also true. I can only speak for us though.
-
The issue is about ecosystem forking (FE is already full of years of .js meaning module), not tooling capabilities.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.