Poll: I use npm, and the JavaScript I write runs...
-
-
Replying to @seldo
…interesting to me how heavy the browser representation here is, given the meta-npm tooling for using npm libs in browser is such a mess
1 reply 0 retweets 4 likes -
Replying to @mcclure111
Agreed. We are very aware of this problem but can only fight so many fires, and the tooling, while complex, is at least solving the problem.
2 replies 0 retweets 8 likes -
Replying to @seldo @mcclure111
I don't understand this logic. It seems better to work on the thing used by a majority, but hey, the mess keeps me busy.
1 reply 0 retweets 2 likes -
Replying to @wycats @mcclure111
By "we" I mean npm Inc. We are trying to keep the registry afloat and improve npm's core; improving webpack is out of scope for now.
2 replies 0 retweets 6 likes -
Replying to @seldo @mcclure111
I don't think npm should improve webpack (wouldn't help Ember), but there are things npm could do to make things generally better for FE.
4 replies 0 retweets 7 likes -
Some (a lot?) is on node core and the modules story. The .mjs proposal is going to wreak havoc on the FE ecosystem, which uses .js for years
2 replies 1 retweet 7 likes -
For non-webpack users*** We should be okay regardless
3 replies 0 retweets 0 likes -
Come on man. Every tool can find a way to support it.
1 reply 0 retweets 0 likes -
That's also true. I can only speak for us though.
2 replies 0 retweets 0 likes
The issue is about ecosystem forking (FE is already full of years of .js meaning module), not tooling capabilities.
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.