This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 682
Atom 1.0 and nuclide not working on OSX #166
Comments
I have the exact same problem. Have you found a solution yet @jonathanstiansen ? |
Sadly I have not :-( On Thu, Aug 13, 2015 at 11:54 AM, Aesop Wolf [email protected]
Jonathan Stiansen |
Okay, so I got it working... I'm sure not all of these steps were necessary:
|
Getting the same issue, I use nvm for my node installation. |
|
It works for me on OSX Yosemite only if I start atom from the command line. I guess that sets up the path properly so it picks node 0.12 |
chenglou
added a commit
to chenglou/nuclide
that referenced
this issue
Mar 22, 2016
Went straight from a JS port to a Reason port here. It's still not as clean as I've hoped for, but we're gonna refactor the whole MerlinService logic soon anyway. This doesn't implement intelligent type hint expansion on selection. This'll come later. **Currently displays OCaml types**. I'll integrate the pretty-printed reason types later. Just wanted to stop changing methods and submit this. Fixes facebookarchive#166. Test plan: - Hover over stuff in a reason file. Should display the type hint correctly right below. - Hover over e.g. a comment. See the region is expanded correctly. - Hover over a semicolon. See no error in console. - Edit the file. Hover again. See correct behaviors.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue addressed this problem earlier: #107
Nuclide requires node .12 atom comes with .10 bundled. Even though node is on my path, it doesn't update the node version in atom - see below.
Node is on my path, and yet it is not working for me. Platform OS X See:
Node is also at the front of my list:
The text was updated successfully, but these errors were encountered: