-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation/Installation Issues: Node Version #848
Comments
Came here to open this. Can't build it either. It complains about
|
Came here to make this issue as well. Still experiencing install issues with fresh clone |
Known issue but this repo is no longer actively maintained, see #853 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current documentation in the README claims that Node 10+ will work.
I'm using Node 16+ currently, and
npm i
will fail on a fresh clone of the repo, and I believe it is because of the version ofnode-sass
being used, but that's just a hunch based on some output wheregyp
was trying to do something with python2. I tried to work around it, but didn't make much progress. There were a few StackOverflow topics, though, that mapped Node versions to versions ofnode-sass
, and that confirmed my suspicion that it was the Node version that I was using that was my issue withnpm i
.After installing
nvm
and installing the last release of Node 10,npm i
also failed because of the usage of optional chaining in the repo, which was first supported in Node 14, IIRC. I was able to get dillinger to succeed withnpm i
with Node 14.21.1As noted in #839 there are some dependencies that need upgrading, it might be worth mentioning this along with a range of working Node versions in the README.
I'd be happy to go over the README and note this, as well as add any clarity or changes as needed in a PR, if that's alright. :) I just discovered dillinger today and plan to use it in my daily workflow and contribute to it!
The text was updated successfully, but these errors were encountered: