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 …
-
Show this thread
-
Side note: This also means there is no difference between `devDependencies` and `dependencies`. Webpack makes sure each deployed service only has what is needed in the bundle.
1 reply 0 retweets 1 likeShow this thread -
Replying to @southpolesteve
There's still a difference. Throwing all your dev deps in `dependencies` just makes it harder for you to distinguish between deps your app needs to run vs ones it needs to dev/test. Think size auditing, etc.
1 reply 0 retweets 0 likes -
Replying to @hichaelmart
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.
1 reply 0 retweets 0 likes -
Replying to @southpolesteve
Why should I? The distinction between dependencies and devDependencies has always been useful – why throw that away? I don't get the impetus.
1 reply 0 retweets 0 likes -
Replying to @hichaelmart @southpolesteve
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?
1 reply 0 retweets 0 likes -
Replying to @hichaelmart
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
1 reply 0 retweets 0 likes -
Replying to @southpolesteve
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 …2 replies 0 retweets 0 likes
Also I actually don't know why cosmos sdk is webpacked. I could see a future where it is not. That's reason enough for me to keep devDeps distinction. I feel your point more for libraries.
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.