Install error about atom-term HOT 18 OPEN

Found this as a workaround, haven't tried it yet myself. But I am facing this issue as well.

EDIT: Disregard. The link I mentioned above reports a different error with pty.js.

from atom-term.

I've run into the same problem. I'm running on Linux Mint 17, probably a configuration header issue.

from atom-term.

I've the same problem on OS X 10.9.4
Any solutions where found ?

from atom-term.

** Same Problem ** (Windows 7 user)

[email protected] install C:\Users\Oneeezy\AppData\Local\Temp\apm-install-dir-114819-8356-11wyxtl\node_modules\term\node_modules\pty.js
node-gyp rebuild

C:\Users\Oneeezy\AppData\Local\Temp\apm-install-dir-114819-8356-11wyxtl\node_modules\term\node_modules\pty.js>node "c:\Program Files\Atom\resources\app\apm\node_modules\atom-package-manager\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere. [C:\Users\Oneeezy\AppData\Local\Temp\apm-install-dir-114819-8356-11wyxtl\node_modules\term\node_modules\pty.js\build\binding.sln]
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere. [C:\Users\Oneeezy\AppData\Local\Temp\apm-install-dir-114819-8356-11wyxtl\node_modules\term\node_modules\pty.js\build\binding.sln]

npm http GET https://registry.npmjs.org/term.js/0.0.3
npm http GET https://registry.npmjs.org/pty.js
npm http GET https://registry.npmjs.org/debounce/0.0.3
npm http GET https://registry.npmjs.org/keypather
npm http 304 https://registry.npmjs.org/keypather
npm http 304 https://registry.npmjs.org/debounce/0.0.3
npm http 304 https://registry.npmjs.org/pty.js
npm http 304 https://registry.npmjs.org/term.js/0.0.3
npm http GET https://registry.npmjs.org/nan/0.7.0
npm http GET https://registry.npmjs.org/extend
npm http 304 https://registry.npmjs.org/nan/0.7.0
npm http 304 https://registry.npmjs.org/extend
gypnpm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the pty.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls pty.js
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\Program Files\Atom\resources\app\apm\node_modules\atom-package-manager\bin\node.exe" "c:\Program Files\Atom\resources\app\apm\node_modules\atom-package-manager\node_modules\npm\bin\npm-cli.js" "--globalconfig" "c:\Program Files\Atom\resources\app\apm\node_modules\atom-package-manager.apmrc" "--userconfig" "C:\Users\Oneeezy.atom.apmrc" "install" "C:\Users\Oneeezy.atom.node-gyp.atom.apm\term\0.2.2\package.tgz" "--target=0.16.0" "--arch=ia32"
npm ERR! cwd C:\Users\Oneeezy\AppData\Local\Temp\apm-install-dir-114819-8356-11wyxtl
npm ERR! node -v v0.10.30
npm ERR! npm -v 1.4.4
npm ERR! code ELIFECYCLE
npm

from atom-term.

Same issue, Linux Mint 17

from atom-term.

Same issue, OS X 10.9.5

from atom-term.

Same issue, Ubuntu 14.04

from atom-term.

Same issue, OS X 10.9.2

from atom-term.

Same issue, OSX 10.10

from atom-term.

Same issue... Like @kon : OS X 10.10.1

from atom-term.

Same issue, Ubuntu 14.04

from atom-term.

Same issue, elementary OS Luna

from atom-term.

Same issue, OSX 10.10.1 atom 0.154.0

from atom-term.

Same issue OSX 10.10.1

from atom-term.

So basically ... this plugin is no longer maintained.

from atom-term.

:( someone forked it and created atom-term2 or something. Not sure why they didn't PR. I was planning on reaching out to them and figuring that out before I reimplement what they have already done

—@tjmehta
Typed using my thumbs..

On Mon, Jan 19, 2015 at 2:55 PM, mikepost [email protected]
wrote:

So basically ... this plugin is no longer maintained.

Reply to this email directly or view it on GitHub:
#25 (comment)

from atom-term.

@tjmehta ,

seeing this also with atom 0.182.0 on ubuntu linux 14.04 lts with unity. same as @schardong @dimascyriaco above.

the forked atom-term2 package you mention in this thread above doesn't install on this set-up either, gives exact same pty.js/node/npm errors.

so will this ever get fixed for the latest atom, please?

best,

— faddah
portland, oregon, u.s.a.

from atom-term.

Im planning on hacking a lot this wkend I’ll try and check this out for you all. Maybe ill merge atom-terms2 fixes in as well.

—
@tjmehta

On Fri, Feb 20, 2015 at 2:07 PM, Faddah Wolf [email protected]
wrote:

@tjmehta ,
seeing this also with atom 0.182.0 on ubuntu linux 14.04 lts with unity. same as @schardong @dimascyriaco above.
the forked atom-term2 package you mention in this thread above doesn't install on this set-up either, gives exact same pty.js/node/npm errors.
so will this ever get fixed for the latest atom, please?
best,
— faddah

portland, oregon, u.s.a.

Reply to this email directly or view it on GitHub:
#25 (comment)

from atom-term.