Open kenrick95 opened 7 years ago
Same issue for me, node 6.9.2 x64, Windows 7 64-bit, Yarn 0.19.1, build works correctly with npm 3.10.8
I'm seeing the same issue on MacOS 10.12.3. npm install leveldown
builds correctly but yarn add leveldown
does not.
Same issue for me
With this combination, yarn add leveldown
works for me now:
I can confirm this is now fixed for me on Windows 10 after upgrading to Yarn 0.20.3.
I know this is a yarnpkg issue tracker, but since this issue was posted based on the results from the cmd yarn install pouchdb
and I found this conversation because of that (having same issue), I thought I would share my two cents as well.
If you are like me and wanting to use PouchDB in the browser only and do not require a backend system, which is what Leveldown/LevelDB if for (if I am not mistaken), you can install PouchDB for the browser only using yarn add pouchdb-browser
[https://pouchdb.com/custom.htmll](PouchDB Custom Page) and eliminate all the hassles and frustrations above.
Also happening for me on:
the same on windows with yarn 0.28.5 on and node 8.4.0
Still happens for me. So what do we do? yarn v0.27.5 node 6.10.0 Windows 10
What we do is continue using npm 3.x for all serious work, "Because newer isn't always better".
yea I agree, I'm going back to using NPM. its not worth trying to wade through all these random errors just to save a few seconds on initial installation with yarn, it costs more time hunting down solutions than just using NPM install.
Any news about this ? I still get this error with yarn
Still having this issue with yarn
Still having this issue yarn : 1.10.1 node : 8.12.0 OS : windows 10 Enterprise 64-bit (10.0, Build 17713)
NPM works, yarn doesnt!!!
Current solution is to clear the cache with :
yarn cache clean
and remove node_modules
folder with :
rm -rf node_modules
Then run yarn
again.
And sometimes a computer restart before running the last step is required 👎
... and for those playing on Windows, rdewolff's solution can be used by changing this line:
rm -rf node_modules
with
rmdir /S /Q node_modules
I just had this issue on a brand new computer, after cloning a project and running yarn
.
Do you want to request a feature or report a bug?
bug
What is the current behavior? Building "leveldown" failed on yarn
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior? npm's behaviour, that succeed on building
Please mention your node.js, yarn and operating system version.
Windows 10 Anniversary Update (Version 10.0.14393), 64-bit
Additional note:
yarn add leveldown