Skip to content
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

in atom terminal plus isn't showing up #397

Open
vamc05 opened this issue Nov 21, 2016 · 34 comments
Open

in atom terminal plus isn't showing up #397

vamc05 opened this issue Nov 21, 2016 · 34 comments

Comments

@vamc05
Copy link

vamc05 commented Nov 21, 2016

atom
screen shot 2016-11-21 at 1 23 18 pm
terminal plus isn't showing up, i have uninstall and same all well it doesn't show up

@gandhiShepard
Copy link

gandhiShepard commented Nov 21, 2016

Yeah, I'm getting this same issue too. If you click on the pink bug icon in the bottom right of your screen shot, you can click to "rebuild" the package. This made TerminalPlus show again. But I can't type in the window. No text input appears.

I do see some error when I open up the inspector. I assume that there were some breaking changes with the latest version of Atom.

BTW, this is an excellent Atom plugin!

@lankford
Copy link

I think it is happening to me as well... I can open a terminal window, but no prompt... just a flashing cursor block... cannot type into it.

@smtl
Copy link

smtl commented Nov 21, 2016

@lankford I am having the same issue. Just installed on version 1.12.5

@gandhiShepard
Copy link

So this is the error I see in the Inspector:

/Applications/Atom.app/Contents/Resources/app.asar/src/task.js:52
Module version mismatch.
Expected 49, got 46. Error: Module version mismatch. Expected 49, got 46.

I'm guessing that this is a core issue? I tried following the path and I didn't find a app.asar directory anywhere

@micage
Copy link

micage commented Nov 22, 2016

The file "~/.atom/packages/terminal-plus/node_modules/pty.js/build/Release/pty.node" is missing. Probably because of node-gyp can not build it. There is also a build error log with a lot of deprecation warnings. Copying pty.node from an older version didn't help either. May installing an older version will work until the issue has been fixed.

@micage
Copy link

micage commented Nov 22, 2016

Solution (that worked for me):

In ~/.atom/packages/terminal-plus/package.json in the dependencies section
remove the commit id (#......) at the end of the pty.js entry:

"pty.js": "git+https://github.com/jeremyramin/pty.js.git#28f2667" becomes
"pty.js": "git+https://github.com/jeremyramin/pty.js.git"

cd ~/.atom/packages/terminal-plus/
npm install
apm rebuild

Restart Atom, should be it ;)

@sfauvart
Copy link

Hello,

I have the same issue on atom v1.12.5 and terminal-plus v0.14.5.

The solution of @micage (thanks! 👍 ) work for me :

edit l.47 of .atom/packages/terminal-plus/package.json

"pty.js": "git+https://github.com/jeremyramin/pty.js.git#28f2667", becomes
"pty.js": "git+https://github.com/jeremyramin/pty.js.git",

run npm install && apm rebuild on .atom/packages/terminal-plus/ directory

restart atom ide, it's ok.

@gandhiShepard
Copy link

That worked! @micage @sfauvart Thanks dewds!

200

@DrewEdwards
Copy link

@sfauvart Worked for me as well! Thanks for the help!

@Vrakfall
Copy link

Vrakfall commented Nov 22, 2016

WOW!

I just installed the package a few days ago and it never worked until I tried this. I thought my python was causing all this because of python3 not being supported by node-gyp and that my python2 wasn't really used. (I'm on Archlinux.) Looks like I was wrong.

Thank you again!

@kupoback
Copy link

Fo me, I followed @sfauvart 's advice however, I can't npm install, whether using sudo or not. This is my error when I sudo.

npm ERR! unpack Could not read data for terminal-plus@0.14.5
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/terminal-plus
npm ERR! 404 
npm ERR! 404  'terminal-plus' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Bug/.atom/packages/terminal-plus/npm-debug.log

Is there something I am misunderstanding? Should I just download the .zip file and install that way?

@Vrakfall
Copy link

Vrakfall commented Nov 23, 2016

What command are you calling where?
It looks like you're trying to do a npm install terminal-plus inside ~.atom/packages/terminal-plus/ which is, of course, redundant. You might also have terminal-plus in a package.json, somewhere, as a dependency. Check on that.

What you should simply do is:

  1. Close atom
  2. Change the said line
  3. Do the following commands
cd ~/.atom/packages/terminal-plus/
npm install
apm rebuild
  1. Restart atom

npm install will go read the required dependencies in the package.json file and install them. This is the normal behaviour when you pass no argument to it.

If you're a yarn user, you might also prefer using yarn install --prod instead of npm install.

Edit: On a side note: you shouldn't use sudo when installing packages locally (in a project directory tree).

@kupoback
Copy link

kupoback commented Nov 23, 2016

@Vrakfall That is exactly what I did last time. Whether I used sudo to npm install or not, the outcome was the same. With that, I am familiar with node.js and using it. I'm just asking if there was something I am missing for the install. I noticed the author asked up to install a separate entity prior to using his plugin, which I also did to try and resolve the issue. None the less, I just returned to using the terminal. Below are my errors though

Last login: Tue Nov 22 16:15:17 on ttys000
Nicks-MacBook-Pro:~ Bug$ cd ~/.atom/packages/terminal-plus/
Nicks-MacBook-Pro:terminal-plus Bug$ sudo npm install
Password:
npm ERR! unpack Could not read data for terminal-plus@0.14.5
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/terminal-plus
npm ERR! 404 
npm ERR! 404  'terminal-plus' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Bug/.atom/packages/terminal-plus/npm-debug.log
Nicks-MacBook-Pro:terminal-plus Bug$ 


Nicks-MacBook-Pro:terminal-plus Bug$ npm install
npm ERR! unpack Could not read data for terminal-plus@0.14.5
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/terminal-plus
npm ERR! 404 
npm ERR! 404  'terminal-plus' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Bug/.atom/packages/terminal-plus/npm-debug.log
Nicks-MacBook-Pro:terminal-plus Bug$ 

@Vrakfall
Copy link

@kupoback Sorry, I was only able to assume what happened based on the few information I had and the way I was able to reproduce it.

What is in your package.json tho? It looks very weird that npm still tries to download terminal-plus by just using npm install.

@sfauvart
Copy link

@kupoback Can you try to uninstall the terminal-plus plugin via the control panel of atom.
After that, reinstall them and retry the trick.
Like @Vrakfall said, it's looks very weird that npm still tries to download terminal-plus.
Note: It's not safe/good practice to run npm as sudo.

@a7madgamal
Copy link

thanks everyone for the solutions, but what about fixing it? :D
It's making the package useless!

@kupoback
Copy link

kupoback commented Nov 23, 2016

@Vrakfall : This is my JSON package. https://codeshare.io/ORDfT

@sfauvart : I tried that also, to no avail. I am going to try and download the repo and drop the folder in there to see if that'll do

EDIT: Here is an update after I unzipped the repo. I was still unable to install and rebuild the package. This is the new JSON package. https://codeshare.io/5RyVo2

@gibffe
Copy link

gibffe commented Nov 23, 2016

Any update on this ? This plugin does not work out of the box with latest Atom.

@Vrakfall
Copy link

Vrakfall commented Nov 23, 2016

@kupoback Weirder and weirder. Is it possible that any of your npm projects/modules contains your .atom folder in some way? I mean, mostly being on top of if or by directory linkings, even some $PATH or environment variables can come into play.

There's definitely something trying to force you install terminal-plus into your terminal-plus folder, which is quite paradoxal. 😝

Would you mind trying to move your directory somewhere else, somewhere freer of interferences, and try to npm install there? Then move it back in and do a apm rebuild inside the same directory.

@gibffe I think it's just a matter of time before the contributors finally notice this issue. ;D

@kupoback
Copy link

kupoback commented Nov 23, 2016

@Vrakfall It is. I mean, I can run npm install on any repo that I started, that has a package.json file in it. But not this one.

Tried it in two spots, the .atom root and my Downloads folder to no avail. :\

Nicks-MacBook-Pro:~ Bug$ cd ~/.atom/__terminal-plus/
Nicks-MacBook-Pro:__terminal-plus Bug$ npm install
npm ERR! unpack Could not read data for terminal-plus@0.14.5
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/terminal-plus
npm ERR! 404 
npm ERR! 404  'terminal-plus' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Bug/.atom/__terminal-plus/npm-debug.log
Nicks-MacBook-Pro:__terminal-plus Bug$ cd ~/Downloads/__terminal-plus/
Nicks-MacBook-Pro:__terminal-plus Bug$ npm install
npm ERR! unpack Could not read data for terminal-plus@0.14.5
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/terminal-plus
npm ERR! 404 
npm ERR! 404  'terminal-plus' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Bug/Downloads/__terminal-plus/npm-debug.log

@Vrakfall
Copy link

@kupoback Let's see if your npm-debug.logs can tell us more about it.

@kupoback
Copy link

@Vrakfall
Copy link

What if you do node-gyp -v?
You mentioned the package's dependencies, are sure you skipped nothing in here?

We can also try by using yarn and see what happens when you yarn install instead of npm install?

@kupoback
Copy link

kupoback commented Nov 23, 2016

I'll try yarn, but I did do node-gyp -v. Running V 3.9.3 I'll report back with an edit

EDIT: Back in business. yarn install worked just fine. Wonder now if there is something wrong with my npm...

@Vrakfall
Copy link

Vrakfall commented Nov 23, 2016

@kupoback That version doesn't even exist. Last one seems to be 3.4.0.
https://github.com/nodejs/node-gyp/releases

Try to reinstall it.

Glad to hear it worked. ^^ This is probably because of the way yarn works, it is deterministic.

On a side note for later, if you plan on keeping yarn, here's a time-saver reminder: don't try to install packages globally with it, yet, because of this: #1060.

@kupoback
Copy link

Weird that it said that version when I installed it last night. Glad it's working though. Should reinstall npm just in case, or maybe just leave it to yarn.

Thank you for the tidbit on #1060!

@Vrakfall
Copy link

@kupoback You're welcome. ^^

I was thinking about reinstalling node-gyp but a npm reinstallation may also be useful. ^^

Enjoy! 😎

@diruuu
Copy link

diruuu commented Nov 24, 2016

Got same problem like @kupoback. I solved it by removed all unnecessary params on package.json. So it looks like this:

{
  "author": {
    "name": "Jeremy Ebneyamin"
  },
  "bugs": {
    "url": "https://github.com/jeremyramin/terminal-plus/issues"
  },
  "dependencies": {
    "atom-space-pen-views": "^2.1.0",
    "pty.js": "git+https://github.com/jeremyramin/pty.js.git",
    "term.js": "git+https://github.com/jeremyramin/term.js.git",
    "underscore": "^1.8.3"
  },
  "description": "A terminal package for Atom, complete with themes and more.",
  "devDependencies": {},
  "engines": {
    "atom": ">=1.2.0"
  },
  "homepage": "https://atom.io/packages/terminal-plus",
  "keywords": [
    "terminal-plus",
    "terminal",
    "plus",
    "panel",
    "tty"
  ],
  "license": "MIT",
  "main": "./lib/terminal-plus",
  "name": "terminal-plus",
  "optionalDependencies": {},
  "repository": {
    "type": "git",
    "url": "git+https://github.com/jeremyramin/terminal-plus.git"
  }
}

then ran npm install && apm rebuild on .atom/packages/terminal-plus/ directory

restart atom ide, and the terminal-plus got back to the business

@MacKentoch
Copy link

Thanks so much @micage and @sfauvart!!!

@dxiaogang
Copy link

The solution of @micage (thanks! 👍 ) work for me too,thanks !

@UncleVic
Copy link

UncleVic commented Dec 6, 2016

Sorry, maybe I'm stupid, but I can't do it.

macOS 10.12.1, Atom 1.12.6, node-gyp 3.4.0, node v7.2.0, npm v3.10.9

I've done that

  1. Close atom
  2. Change the said line
  3. Do the following commands
cd ~/.atom/packages/terminal-plus/
npm install
apm rebuild
  1. Restart atom

But I see black screen and blincking cursor ;(
What am I doing wrong?

platformio-ide-terminal dosen't work too.

@ashishwadekar
Copy link

@diruuu Thanks for the solution. Worked like a charm. Cheers 👍

@mylastore
Copy link

mylastore commented Nov 9, 2019

on ARCH LINUX

I did the above and still have the same error and plus all terminal packages I install on Atom do not work I am new to Atom and can't understand why the most important package is not build in just like all the other IDE's well is free so can't complained about not been perfect.

gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.3.8-arch1-1
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/oquinteros/.atom/packages/terminal-plus/node_modules/pty.js
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pty.js@0.3.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the pty.js@0.3.1 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:

@sagarujjwal
Copy link

Thankyou very much. I have spend almost 1 hour to find the solution but didn't get much.
you have solved my problem :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests