# Atom 1.39 won't build julia-client

**URL:** https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696
**Category:** Juno
**Created:** [July 23, 2019, 6:10pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696 "2019-07-23T18:10:47Z")
**Posts on this page:** 20
**Page:** 2

<div class="post-metadata">

### Author: ![gabehassler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gabehassler/32/13848_2.png) [@gabehassler](https://discourse.julialang.org/u/gabehassler)
#### Post date: [July 26, 2019, 10:18pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/22 "2019-07-26T22:18:43Z")

</div>

Thanks for reporting in. I just tried it and everything looks good. I appreciate all the work you did getting this back up and running (and all the work you do for Juno generally)!

---

<div class="post-metadata">

### Author: ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [July 27, 2019, 4:54am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/23 "2019-07-27T04:54:40Z")

</div>

Thank you for the fix. Kudos for the quick response!

---

<div class="post-metadata">

### Author: ![StevenSiew](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevensiew/32/218393_2.png) [@StevenSiew](https://discourse.julialang.org/u/StevenSiew)
#### Post date: [July 27, 2019, 6:27am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/24 "2019-07-27T06:27:00Z")

</div>

In the mean time

On my mac

1. on my running atom
2. select atom - preferences - core - core settings
3. uncheck “Automatically update”

Regards  
Steven Siew

---

<div class="post-metadata">

### Author: ![HarryG](https://avatars.discourse-cdn.com/v4/letter/h/7bcc69/32.png) [@HarryG](https://discourse.julialang.org/u/HarryG)
#### Post date: [July 27, 2019, 7:58am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/25 "2019-07-27T07:58:50Z")

</div>

I can also confirm that julia-client@0.8.12-beta2 works with Atom 1.39.1 on macOS 10.14.6.

Thank you, pfitzseb!

---

<div class="post-metadata">

### Author: ![alejandromerchan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/alejandromerchan/32/10500_2.png) [@alejandromerchan](https://discourse.julialang.org/u/alejandromerchan)
#### Post date: [July 28, 2019, 1:26pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/27 "2019-07-28T13:26:33Z")

</div>

After a few days without it, yesterday I reinstalled everything on my Manjaro machine and I have Atom-Juno back. I also updated my seldom used Windows machine and it also works. Thanks for the fix!

---

<div class="post-metadata">

### Author: ![Karajan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/karajan/32/8545_2.png) [@Karajan](https://discourse.julialang.org/u/Karajan)
#### Post date: [July 29, 2019, 6:31am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/28 "2019-07-29T06:31:47Z")

</div>

Could you tell me what exactly you reinstalled? On Manjaro, I had to resort to downloading Atom from their website.

---

<div class="post-metadata">

### Author: ![HelgavonLichtenstein](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/helgavonlichtenstein/32/5005_2.png) [@HelgavonLichtenstein](https://discourse.julialang.org/u/HelgavonLichtenstein)
#### Post date: [July 29, 2019, 8:33am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/29 "2019-07-29T08:33:37Z")

</div>

I tried following these steps but run into trouble at step 4.

![image](https://global.discourse-cdn.com/julialang/original/3X/5/5/559936c8e941e949225a8ff0dc3b2bbee2a21ad6.png)

What should I do?

---

<div class="post-metadata">

### Author: ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [July 29, 2019, 8:43am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/30 "2019-07-29T08:43:53Z")

</div>

The program is probably here: `C:\Users\HelgavonLichtenstein\AppData\Local\atom\bin `.

---

<div class="post-metadata">

### Author: ![HelgavonLichtenstein](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/helgavonlichtenstein/32/5005_2.png) [@HelgavonLichtenstein](https://discourse.julialang.org/u/HelgavonLichtenstein)
#### Post date: [July 29, 2019, 9:02am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/31 "2019-07-29T09:02:12Z")

</div>

> [@PetrKryslUCSD](#):
>
> `C:\Users\HelgavonLichtenstein\AppData\Local\atom\bin`

I do not know what to do with this information.

I have installed the latest Atom version based on comments from [another thread](https://discourse.julialang.org/t/cannot-install-julia-client-0-8-10-in-atom-using-uber-juno/26300/17) stating Julia now works with the latest Atom version.

(And it works!)

---

<div class="post-metadata">

### Author: ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [July 29, 2019, 9:03am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/32 "2019-07-29T09:03:08Z")

</div>

If you wish to run apm, you can do `C:\Users\HelgavonLichtenstein\AppData\Local\atom\bin\apm install ....`.

---

<div class="post-metadata">

### Author: ![HarryG](https://avatars.discourse-cdn.com/v4/letter/h/7bcc69/32.png) [@HarryG](https://discourse.julialang.org/u/HarryG)
#### Post date: [July 29, 2019, 10:23am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/33 "2019-07-29T10:23:30Z")

</div>

Hello Helga, the workaround I proposed was for macOS where apm (the Atom package manager) is installed in a different location than it is on Windows, as indicated by PetrKryslUCSD.

I marked my proposal as obsolete soon after pfitzseb made julia-client 0.8.12-beta2 available which fixed the problem. I’m glad to read that Julia/Juno runs again on your machine as well. Kind regards!

---

<div class="post-metadata">

### Author: ![alejandromerchan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/alejandromerchan/32/10500_2.png) [@alejandromerchan](https://discourse.julialang.org/u/alejandromerchan)
#### Post date: [July 29, 2019, 4:07pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/34 "2019-07-29T16:07:53Z")

</div>

I did several things , but the most important one was to make sure I was using the latest version of julia-client (0.8.12-beta2). I had erased everything from Atom from my computer and from Julia, then reinstalled the latest version of Atom and the julia-client. That worked. I also have a laptop with Manjaro, on that one I didn’t erase Atom, but did erase the Julia packages and reinstall them. Both computers are working, the laptop needed a reboot, but works now.

---

<div class="post-metadata">

### Author: ![phlavenk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/phlavenk/32/1873_2.png) [@phlavenk](https://discourse.julialang.org/u/phlavenk)
#### Post date: [July 30, 2019, 4:30am UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/35 "2019-07-30T04:30:16Z")

</div>

I’ve also experienced the reported problems, but I just waited few days (over weekend) and on Monday atom upgraded itself to 1.39.1 and afterwards julia-client updated automatically to 0.8.12-beta2.  
I didn’t have to manually delete or change anything. And this is the exact behavior I’d expect of inteaction of two well maintained packages as Atom and Juno are.

---

<div class="post-metadata">

### Author: ![aalexandersson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aalexandersson/32/2927_2.png) [@aalexandersson](https://discourse.julialang.org/u/aalexandersson)
#### Post date: [August 13, 2019, 2:53pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/36 "2019-08-13T14:53:23Z")

</div>

The same problem exists also on Atom 1.40 (Windows 7, x64). I cannot update julia-client from 0.8.1 to the latest 0.9.4 because “No prebuilt binaries found”.

```julia
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

F:\>apm update
Package Updates Available (1)
└── julia-client 0.8.1 -> 0.9.4

Would you like to install these updates? (yes) yes

Installing julia-client@0.9.4 to C:\Users\aalexandersson\.atom\packages failed

> @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install C:\Users\AALEXA~1\AppData\
Local\Temp\apm-install-dir-119713-9060-affr9z.lfwy\node_modules\julia-client\nod
e_modules\@pfitzseb\node-pty-prebuilt
> prebuild-install || node scripts/install.js

C:\Users\AALEXA~1\AppData\Local\Temp\apm-install-dir-119713-9060-affr9z.lfwy\nod
e_modules\julia-client\node_modules\@pfitzseb\node-pty-prebuilt>if not defined n
pm_config_node_gyp (node "C:\Users\aalexandersson\AppData\Local\atom\app-1.40.0\
resources\app\apm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\.
.\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\aalexan
dersson\AppData\Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_mo
dules\node-gyp\bin\node-gyp.js" rebuild )

prebuild-install WARN install No prebuilt binaries found (target=3.1.10 runtime=
node arch=x64 libc= platform=win32)
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\Users\aalexandersson\AppData
\Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_modules\node-gyp\
lib\configure.js:492:19)
gyp ERR! stack at PythonFinder.<anonymous> (C:\Users\aalexandersson\AppData\
Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_modules\node-gyp\l
ib\configure.js:517:16)
gyp ERR! stack at C:\Users\aalexandersson\AppData\Local\atom\app-1.40.0\reso
urces\app\apm\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:182:21)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Users\\aalexandersson\\AppData\\Local\\atom\\app-1.40.0\\r
esources\\app\\apm\\bin\\node.exe" "C:\\Users\\aalexandersson\\AppData\\Local\\a
tom\\app-1.40.0\\resources\\app\\apm\\node_modules\\npm\\node_modules\\node-gyp\
\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\AALEXA~1\AppData\Local\Temp\apm-install-dir-119713-9060-af
fr9z.lfwy\node_modules\julia-client\node_modules\@pfitzseb\node-pty-prebuilt
gyp ERR! node -v v10.2.1
gyp ERR! node-gyp -v v3.7.0
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\AALEXA~1\AppDa
ta\Local\Temp\apm-install-dir-119713-9060-affr9z.lfwy\package.json'
npm WARN apm-install-dir-119713-9060-affr9z.lfwy No description
npm WARN apm-install-dir-119713-9060-affr9z.lfwy No repository field.
npm WARN apm-install-dir-119713-9060-affr9z.lfwy No README data
npm WARN apm-install-dir-119713-9060-affr9z.lfwy No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install: `prebuild-install
|| node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install scrip
t.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\aalexandersson\.atom\.apm\_logs\2019-08-13T14_37_39_520Z-d
ebug.log

F:\>apm uninstall ink
Uninstalling ink done

F:\>apm uninstall julia-client
Uninstalling julia-client done

F:\>apm install ink
Installing ink to C:\Users\aalexandersson\.atom\packages done

F:\>apm install julia-client
Installing julia-client to C:\Users\aalexandersson\.atom\packages failed

> @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install C:\Users\AALEXA~1\AppData\
Local\Temp\apm-install-dir-119713-6468-kounnt.3de8\node_modules\julia-client\nod
e_modules\@pfitzseb\node-pty-prebuilt
> prebuild-install || node scripts/install.js

C:\Users\AALEXA~1\AppData\Local\Temp\apm-install-dir-119713-6468-kounnt.3de8\nod
e_modules\julia-client\node_modules\@pfitzseb\node-pty-prebuilt>if not defined n
pm_config_node_gyp (node "C:\Users\aalexandersson\AppData\Local\atom\app-1.40.0\
resources\app\apm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\.
.\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\aalexan
dersson\AppData\Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_mo
dules\node-gyp\bin\node-gyp.js" rebuild )

prebuild-install WARN install No prebuilt binaries found (target=3.1.10 runtime=
node arch=x64 libc= platform=win32)
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\Users\aalexandersson\AppData
\Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_modules\node-gyp\
lib\configure.js:492:19)
gyp ERR! stack at PythonFinder.<anonymous> (C:\Users\aalexandersson\AppData\
Local\atom\app-1.40.0\resources\app\apm\node_modules\npm\node_modules\node-gyp\l
ib\configure.js:517:16)
gyp ERR! stack at C:\Users\aalexandersson\AppData\Local\atom\app-1.40.0\reso
urces\app\apm\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:182:21)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Users\\aalexandersson\\AppData\\Local\\atom\\app-1.40.0\\r
esources\\app\\apm\\bin\\node.exe" "C:\\Users\\aalexandersson\\AppData\\Local\\a
tom\\app-1.40.0\\resources\\app\\apm\\node_modules\\npm\\node_modules\\node-gyp\
\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\AALEXA~1\AppData\Local\Temp\apm-install-dir-119713-6468-ko
unnt.3de8\node_modules\julia-client\node_modules\@pfitzseb\node-pty-prebuilt
gyp ERR! node -v v10.2.1
gyp ERR! node-gyp -v v3.7.0
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\AALEXA~1\AppDa
ta\Local\Temp\apm-install-dir-119713-6468-kounnt.3de8\package.json'
npm WARN apm-install-dir-119713-6468-kounnt.3de8 No description
npm WARN apm-install-dir-119713-6468-kounnt.3de8 No repository field.
npm WARN apm-install-dir-119713-6468-kounnt.3de8 No README data
npm WARN apm-install-dir-119713-6468-kounnt.3de8 No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install: `prebuild-install
|| node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install scrip
t.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\aalexandersson\.atom\.apm\_logs\2019-08-13T14_41_36_931Z-d
ebug.log

F:\>

```

---

<div class="post-metadata">

### Author: ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [August 13, 2019, 5:34pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/37 "2019-08-13T17:34:16Z")

</div>

Hm, not sure why you’re seeing that error – everything works fine for me on Windows 10 and

```julia
Atom : 1.40.0
Electron: 3.1.10
Chrome : 66.0.3359.181
Node : 10.2.0

```

Can you give me the output of `atom -v`, just to be sure?

---

<div class="post-metadata">

### Author: ![aalexandersson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aalexandersson/32/2927_2.png) [@aalexandersson](https://discourse.julialang.org/u/aalexandersson)
#### Post date: [August 13, 2019, 6:59pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/38 "2019-08-13T18:59:50Z")

</div>

I get the same output from the command prompt:

```julia
F:\>atom -v

Atom : 1.40.0
Electron: 3.1.10
Chrome : 66.0.3359.181
Node : 10.2.0

```

Edit: Added result of `versioninfo()`:

```julia
julia> versioninfo()
Julia Version 1.1.0
Commit 80516ca202 (2019-01-21 21:24 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, nehalem)

```

---

<div class="post-metadata">

### Author: ![mwsohn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mwsohn/32/2696_2.png) [@mwsohn](https://discourse.julialang.org/u/mwsohn)
#### Post date: [August 14, 2019, 3:51pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/39 "2019-08-14T15:51:15Z")

</div>

I do have the same problem. I am running Julia 1.1.1 on Win10. I have attempted to uninstall and reinstall Atom multiple times but julia-client (0.9.4) fails to install.

---

<div class="post-metadata">

### Author: ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [August 14, 2019, 3:54pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/40 "2019-08-14T15:54:38Z")

</div>

This appears to be the same issue we had when Atom 1.39 was released, so I’m very surprised that the fix for that doesn’t work for some people.

Do you have any weird antivir software running that might delete the binaries we ship, so that we then try to compile them ourselves? I can’t reproduce this issue anymore on a fairly clean Windows VM.

---

<div class="post-metadata">

### Author: ![mwsohn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mwsohn/32/2696_2.png) [@mwsohn](https://discourse.julialang.org/u/mwsohn)
#### Post date: [August 14, 2019, 5:43pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/41 "2019-08-14T17:43:25Z")

</div>

No. Just Windows Defender. I even tried to install julia-client with real time protection off. It was not successful.

---

<div class="post-metadata">

### Author: ![damonturney](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@damonturney](https://discourse.julialang.org/u/damonturney)
#### Post date: [August 14, 2019, 6:22pm UTC](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696/42 "2019-08-14T18:22:05Z")

</div>

I am on a Mac (Mojave) with Julia Version 1.1.0 (2019-01-21) and  
Atom : 1.40.0  
Electron: 3.1.10  
Chrome : 66.0.3359.181  
Node : 10.2.0

Of course I get the error when I try to install julia-client@0.9.4 .

I ALSO get the following error when I try to install julia-client@0.8.12-beta2

apm install julia-client@0.8.12-beta2  
Installing julia-client@0.8.12-beta2 to /Users/damon/.atom/packages ✗

> @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install /private/var/folders/z8/fj99333d6\_qgthzpz7j7kxk00000gn/T/apm-install-dir-119714-6112-8zi1st.41lk/node\_modules/julia-client/node\_modules/@pfitzseb/node-pty-prebuilt  
> prebuild-install || node scripts/install.js

npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to “coffeescript” (no hyphen)  
prebuild-install WARN install No prebuilt binaries found (target=3.1.10 runtime=node arch=x64 libc= platform=darwin)  
gyp ERR! configure error  
gyp ERR! stack Error: Python executable “/Applications/Atom.app/Contents/Resources/app/apm/bin/python-interceptor.sh” is v3.6.8, which is not supported by gyp.  
gyp ERR! stack You can pass the --python switch to point to Python \>= v2.5.0 & \< 3.0.0.  
gyp ERR! stack at PythonFinder.failPythonVersion (/Applications/Atom.app/Contents/Resources/app/apm/node\_modules/npm/node\_modules/node-gyp/lib/configure.js:501:19)  
gyp ERR! stack at PythonFinder. (/Applications/Atom.app/Contents/Resources/app/apm/node\_modules/npm/node\_modules/node-gyp/lib/configure.js:483:14)  
gyp ERR! stack at ChildProcess.exithandler (child\_process.js:282:7)  
gyp ERR! stack at ChildProcess.emit (events.js:182:13)  
gyp ERR! stack at maybeClose (internal/child\_process.js:961:16)  
gyp ERR! stack at Socket.stream.socket.on (internal/child\_process.js:380:11)  
gyp ERR! stack at Socket.emit (events.js:182:13)  
gyp ERR! stack at Pipe.\_handle.close [as \_onclose] (net.js:596:12)  
gyp ERR! System Darwin 18.7.0  
gyp ERR! command “/Applications/Atom.app/Contents/Resources/app/apm/bin/node” “/Applications/Atom.app/Contents/Resources/app/apm/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js” “rebuild”  
gyp ERR! cwd /private/var/folders/z8/fj99333d6\_qgthzpz7j7kxk00000gn/T/apm-install-dir-119714-6112-8zi1st.41lk/node\_modules/julia-client/node\_modules/@pfitzseb/node-pty-prebuilt  
gyp ERR! node -v v10.2.1  
gyp ERR! node-gyp -v v3.7.0  
gyp ERR! not ok  
npm WARN enoent ENOENT: no such file or directory, open ‘/private/var/folders/z8/fj99333d6\_qgthzpz7j7kxk00000gn/T/apm-install-dir-119714-6112-8zi1st.41lk/package.json’  
npm WARN apm-install-dir-119714-6112-8zi1st.41lk No description  
npm WARN apm-install-dir-119714-6112-8zi1st.41lk No repository field.  
npm WARN apm-install-dir-119714-6112-8zi1st.41lk No README data  
npm WARN apm-install-dir-119714-6112-8zi1st.41lk No license field.

npm ERR! code ELIFECYCLE  
npm ERR! errno 1  
npm ERR! @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install: `prebuild-install || node scripts/install.js`  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the @pfitzseb/node-pty-prebuilt@0.8.1-prebuilt3 install script.  
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/damon/.atom/.apm/\_logs/2019-08-14T17\_59\_10\_124Z-debug.log

[Previous page](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696.md?page=1)

[Next page](https://discourse.julialang.org/t/atom-1-39-wont-build-julia-client/26696.md?page=3)
