Yarn support #44
Comments
|
Possibly! how does yarn install binaries? |
|
You mean the command to do so? the official website might be a little tricky to find as it's not the 1st result, at least for me (https://yarnpkg.com/en/) Ah, please let me know if there's something I could contribute with in this matter. I think the current version of this vs. @8.9.4 is quite different (particularly |
|
Mmm. I don't use yarn at all, so I'm not sure with how it differs from how npm installs packages. Where does it put binaries if not in node_modules/.bin? (I can do the digging, but any help and context you can give will speed it up!) |
|
It should be inside node_modules/.bin as well. When I use npm install [email protected], it shows that it runs My first guess when I first noticed the issue, was whether it was running the preinstall script at all. But it's probably an issue within
|
|
Oh interesting! Does yarn generally skip scripts like that? |
|
No, not really. Just did a quick test and it calls a "pre" script just fine. |
|
Interesting. I'll have to dig into why, unless someone else gets to it first! |
|
Thanks a lot for taking the time to! 😄 |
Use .nvmrc to indicate desired version for now. The `engines` object is pretty much useless to anything outside of Heroku since it doesn't enforce a strict requirement. Investigated using the node package [1] to install a specific version of the node binary as a requirement, but there's controversy over bloat factor [2, 3] and it is not yet fully compatible with yarn [4]. [1] https://www.npmjs.com/package/node [2] https://twitter.com/housecor/status/962347301456015360 [3] https://twitter.com/maybekatz/status/958157474397171712 [4] aredridel/node-bin-gen#44
* Jump to node 9.8.0 Use .nvmrc to indicate desired version for now. The `engines` object is pretty much useless to anything outside of Heroku since it doesn't enforce a strict requirement. Investigated using the node package [1] to install a specific version of the node binary as a requirement, but there's controversy over bloat factor [2, 3] and it is not yet fully compatible with yarn [4]. [1] https://www.npmjs.com/package/node [2] https://twitter.com/housecor/status/962347301456015360 [3] https://twitter.com/maybekatz/status/958157474397171712 [4] aredridel/node-bin-gen#44 * Bump to node-sass 4.7.2 Node 9.8.0 was not happy with previous version lock (4.5.3). * Upgrade to Nuxt 1.4.0 Previously running pre-production release. Includes following adjustments: * Tweak Nuxt config for eslint (passing context) * Swap in `eslint-plugin-vue` for `eslint-plugin-html` & use it along with standard for base rules * Fix alias for components to align with Nuxt 1.x [1] * Export state as function for Vuex store, since using modules mode [2] [1] https://nuxtjs.org/guide/directory-structure#aliases [2] https://nuxtjs.org/guide/vuex-store#modules-mode * Replace nuxt-helpers/axios with axios module As indicated in initial implementation of fetching data back in 42d0f7e. Nuxt modules have come a long way in the past year. Basically follow the documentation [1] to swap out the helper for the module. The module makes axios widely available across the app: * plugins * vuex store * pages * middleware * other modules But notice this does not include external utility files, which is a necessity here for `utils/libcal.js`. The workaround was to pass `this.$axios` from the store to the util as a param. Not sure this will be the longterm solution since there are ongoing discussions in the module repo on potential options on better sharing the configured axios instance with external files. [1] https://axios.nuxtjs.org * Drop add package Never used. Mistakenly introduced in ca06ecd as part of #20. * Upgrade packages to latest And satisfy unmet peer dependencies. * Bump app version to 0.2.0
|
The cause of the problem is yarnpkg/yarn#3421. The workaround is yarnpkg/yarn#3421 (comment). |
|
Note that this package doesn't work with PnP, which is the "algorithm" used by Yarn 2 and which is opt-in in yarn 1: yarnpkg/berry#637 (comment) |
Good evening!
I've noticed
yarn add [email protected]doesn't really add the binaries tonode_modules/.bin, whereas npm does. Would it be possible to support yarn as well?Thanks!
The text was updated successfully, but these errors were encountered: