-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
yarn install yields errors on node v12 #7
Comments
Hello, I know too little about the toolchain to document which are good versions. If you have found a set that works, I would appreciate a lot If you added a section to the README about it. Cheers! |
I'm learning here too. As of right now my toolchain looks like this:
(In fact, having queried all those versions one at a time, I see an inconsistency I hadn't noticed before ... I probably ought to update It's pretty tedious getting dependencies from three different sources (the language runtimes, the npm packages, and the clojure packages) -- I just might be lazy enough to write a script for that. |
I put it all into a short script written in joker. It queries the environment and prints a map with sorted keys:
Anyway I'll clean that up and send as a pull request (along with a section in the readme stating these tool versions) later this week. That way, I'd like to think other developers could post new configurations that they have had success with, and all of that can be compiled into a table of some sort. |
TL;DR: for documentation purposes, would you consider documenting "known good" versions of the development toolchain?
in the
shadow-cljs
documentation is where you'll find the dependency on JDK 1.8.running
yarn install
with node v12 results in a bunch of build errors fromfsevents
. See the transcript below. Granted, the last entry in the log says you can ignore this entry but to be honest I didn't know if I should believe that message or not.Tracking these version issues down took me longer than 3 minutes, and while educational, it was friction I would have appreciated not having to suffer as a newcomer.
Details below the line.
Here's why that dependency is there:
And incidentally the build issue is supposedly fixed with this pull request resulting in
fsevents@1.2.9
, and this pull request injest-haste-map
, and I suppose eventually the updated package will work it's way into react native too.The text was updated successfully, but these errors were encountered: