-
Notifications
You must be signed in to change notification settings - Fork 162
doesn't work with atom 1.12 #85
Comments
there is an error when opening the console task.coffee:86 Cannot find module '..\bin\win32\ia32.m49.node' Error: Cannot find module '..\bin\win32\ia32.m49.node'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object.<anonymous> |
+1 |
Have the same issue after upgrading to Atom 1.12 on MacOSX,
then after this appears I get this error,
These errors do not appear until after you try opening a new terminal tab. |
probably need to upgrade nan but I'm not sure if this project is still maintained which is unfortunate. |
Sometimes perfection doesn't need an update lol. Give em some time, coming from a software engineer background myself, I believe this is ran by company so they'll probably need to schedule time for one of their engineers to check it out during one of their next sprints. |
I think this is the same issue I have. On opening a terminal I get a console warning:
Which it says originates in That is followed by an error stacktrace:
Which it says originates in And then after that another error stacktrace:
Which it says also originates in Screenshot for full console details. Atom 1.12.0-beta3, OSX 10.11.6. Is it possible it just failed to build some native module on install (there was no error - popup or console - on install)? |
I see that we will have a tons of problems with new Atom 1.12. They switched to new Electron and other packages that require new NAN and other things. The Please don't use Atom 1.12 and wait when we preapre all PTY binaries. |
Thanks for the update. |
Can't use 1.11 because it breaks some mandatory packages. EDIT: https://github.com/tjmehta/terminal-plus working on 1.12 beta5
|
See also jeremyramin#364 |
Was having the exact same issues with installed versions of stable or beta. Then I used the stand alone windows exe and installed platformio-ide-terminal package. That seems to work, so far. |
@alexrussell I'm seeing the same error as you on OSX, Atom 1.12-beta7: UPD: OK, here's my temporary workaround: 😆 |
Wow.... 12 comments... multiple ups ( 👍 ) Need to resovle this issue... P.S: Is here someone with Ubuntu? |
@kachkaev haha nice workaround :) And no I didn't find anything that I found particularly satisfactory - like you I'm just using separate terminals for now. @ivankravets from the looks of comments on both this and the original terminal-plus package (as well as other people's forks) it's all about updating the version numbers (commit references) for the dependent packages pty.js and term.js (I think actually just pty.js). But other than that (presumably they need to have native modules built for each platform and something needs tweaking and that's why the updates are required) I don't know much of the root of the issue. |
@alexrussell we have own PlatformIO's fork of PTY with pre-built binaries. It allows to use PlatformIO IDE Terminal on the machine where compiler is not installed for gyp. Yes, I know that we should update As result, we've just succesfully compiled PTY.JS for Windows and tested on Windows 8/10 and are working on other binaries for macOS & Linux. Stay tuned! 😊 Also, don't forget to try http://platformio.org 😆 |
A-ha good news. As for trying PlatformIO, I'd love to play around with and learn new things but I have enough on my plate at the moment! :) |
PlatformIO IDE Terminal 2.2.1 is out! P.S: Atom 1.12 for Linux is not ready. Please comment here if you are Ubuntu owner and would like to help us. |
works good for me as well. thanks. |
Glad to help 😃 I'm planning on cleaning up the pty.js situation and improving Windows support soon. Follow microsoft/vscode#13625 if you want to track that development. |
I'm using windows 10, configured the package to use git bash as the exectuable and it all worked well for some time.
However with the new atom 1.12 beta it is just opening a new panel but the shell inside is not started.
there are no errors in the console.
The text was updated successfully, but these errors were encountered: