Skip to content
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.

Atom 1.0 and nuclide not working on OSX #166

Open
jonathanstiansen opened this issue Aug 9, 2015 · 6 comments
Open

Atom 1.0 and nuclide not working on OSX #166

jonathanstiansen opened this issue Aug 9, 2015 · 6 comments

Comments

@jonathanstiansen
Copy link

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:
screen shot 2015-08-08 at 4 00 28 pm
Node is also at the front of my list:
screen shot 2015-08-08 at 4 10 03 pm

@aesopwolf
Copy link

I have the exact same problem. Have you found a solution yet @jonathanstiansen ?

@jonathanstiansen
Copy link
Author

Sadly I have not :-(

On Thu, Aug 13, 2015 at 11:54 AM, Aesop Wolf [email protected]
wrote:

I have the exact same problem. Have you found a solution yet
@jonathanstiansen https://github.com/jonathanstiansen ?


Reply to this email directly or view it on GitHub
#166 (comment).

Jonathan Stiansen
P. 778.999.0534

@aesopwolf
Copy link

Okay, so I got it working... I'm sure not all of these steps were necessary:

  1. uninstall atom by dragging from Applications folder to the Trash
  2. install atom using brew cask install atom
  3. which apm
  4. rm -rf /usr/local/bin/apm
  5. Open Atom, from the "Atom" menu choose "Install Shell Commands"

@balupton
Copy link

Getting the same issue, I use nvm for my node installation.

@balupton
Copy link

$ ~/Applications/Atom.app/Contents/Resources/app/apm/bin/apm -v
apm  1.0.4
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.5.1
$ node -v
v3.0.0

@pastur
Copy link

pastur commented Sep 9, 2015

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants