The lack of frameworks in node is not a community choice, it is a technical limitation of npm.
-
-
Replying to @robotlolita
@robotlolita npm strongly discourages (aka it's broken) patterns where multiple packages share a single instance of a dependent module.2 replies 1 retweet 1 like -
Replying to @wycats
@wycats@robotlolita nested deps is a feature not a bug! otherwise you end up with versioning nightmares which I would assume you know.5 replies 0 retweets 1 like -
Replying to @brianleroux
@brianleroux@wycats@robotlolita it sure beats the ruby nightmares of two packages wanting different versions of something.2 replies 0 retweets 2 likes -
Replying to @fritzy
@fritzy@brianleroux@robotlolita I have probably spent more time waiting for npm cache clear them solving all Ruby dep issues ever.1 reply 1 retweet 0 likes -
Replying to @wycats
@wycats@brianleroux@robotlolita I used to see ruby projects where dependencies would move and break a project due to dep version conflicts1 reply 0 retweets 0 likes
@fritzy @brianleroux @robotlolita This is after bundler?
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.