In nodejs world, I bet we'll see more people code splitting their backends. Develop in a monorepo and deploy to code split + webpacked microservices or cloud functions.https://twitter.com/samccone/status/1017813420907876352 …
why not inspect the bundles directly? package.json is a point in time capture of what a human thought was needed to run the app. bundle analyzers are a computer and will give you a better answer.
-
-
Why should I? The distinction between dependencies and devDependencies has always been useful – why throw that away? I don't get the impetus.
-
You're saying to understand a project's deps you should run webpack first...? You're throwing out best practice for... I'm not sure what?
-
I see it as an error-prone practice. deps vs devDeps feels like a repo lifetime experiment at how good your devs are at typing CLI flags. So if doing something like running webpack removes that then

-
Wow, couldn't disagree more. But you know, if that's your personal style – I'll help you along and open a PR in 3... 2...
https://github.com/Azure/azure-cosmos-js/blob/master/package.json#L33-L60 … -
I don't feel that strongly about it. Not enough to change some repo I just dropped into. Its more "oh hey, I prob don't have to rememebr to type --save-dev on greenfield webpacked fns. Thats nice."
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.