I still have no idea where yarn 2 actually installs packages... as far as I can tell, it, doesn't
-
Show this thread
-
$ node > require('lodash') Uncaught Error: Cannot find module 'lodash' $ yarn node > require('lodash') <ref *1> [Function: lodash] { templateSettings: { ... }, after: [Function: after], ary: [Function: ary], assign: [Function (anonymous)], ... } what
1 reply 0 retweets 7 likesShow this thread -
we already have decade-established conventions for where you put packages so that node.js, browserify, webpack et al can find them, what are you doing
1 reply 1 retweet 5 likesShow this thread -
it's already a big problem that e.g. rails is so tightly coupled to yarn, and now yarn is going "you have to run your entire program through our binary or it won't work"?
3 replies 1 retweet 9 likesShow this thread -
also the start-up time of yarn 2 is *appalling*
1 reply 0 retweets 3 likesShow this thread -
it reminds me of command-line tools someone decided to write on the jvm, which is a really bad choice for such things
1 reply 0 retweets 3 likesShow this thread -
it took us years to get consensus around how JS modules should work and now yarn is going "if you want to run anything you got from the npm registry, you have to use our runtime"
4 replies 2 retweets 10 likesShow this thread
yikes
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.