-
I'm trying to follow the sparse steps listed on the contribute page, but no matter what I try the I've tried directly on my windows 10 system, I've tried in WSL Ubuntu-20.04, and I've tried on a VM with Ubuntu-22.04. They all fail. The windows one fails most spectacularly, not even getting to the node-sass build, but both of the Linux versions fail at the same spot.
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 4 replies
-
Thanks for being willing to try contributing. Your output implies you're using Node v20. Please see the advice at https://vscode-sqltools.mteixeira.dev/en/contributing/building about this project requiring v14, and suggesting the use of |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
What yarn version do you have? I'm using v1.22.19 from https://classic.yarnpkg.com/lang/en/ |
Beta Was this translation helpful? Give feedback.
-
1.22.19 as well, I installed it using the Debian/Ubuntu instructions here https://classic.yarnpkg.com/en/docs/install#debian-stable - So I assume it should be the same thing. My |
Beta Was this translation helpful? Give feedback.
-
Alright, I got it. Your questions helped give me the hint that I uninstalled all versions of node, uninstalled nvm, uninstalled npm, and uninstalled yarn (pretty much just nuked everything). After that I installed yarn first, then nvm, then installed version 14.21.3 (I noticed before I was using an older version of 14.x, so thought that might help. It didn't help by itself, I tried using this version via nvm previously). Once yarn, nvm, and only node 14.21 was installed I re-cloned the repo and ran So I guess the answer is if you get an error similar to mine up above, just remove everything and try again without any potentially conflicting node or yarn versions installed? It looks like everything is now working according to design. Thanks! |
Beta Was this translation helpful? Give feedback.
-
This is a very useful post, and does not show up in discussions automatically as it is marked as closed. Consider keeping this open? |
Beta Was this translation helpful? Give feedback.
Alright, I got it. Your questions helped give me the hint that
yarn
or thenode
version were probably the culprit.I uninstalled all versions of node, uninstalled nvm, uninstalled npm, and uninstalled yarn (pretty much just nuked everything). After that I installed yarn first, then nvm, then installed version 14.21.3 (I noticed before I was using an older version of 14.x, so thought that might help. It didn't help by itself, I tried using this version via nvm previously).
Once yarn, nvm, and only node 14.21 was installed I re-cloned the repo and ran
yarn
. This time it succeeded!So I guess the answer is if you get an error similar to mine up above, just remove everything and try again wit…