I am relatively new to Node. I am using Atom and the following error message keeps popping up over and over again:
child process error: Error: channel closed
Additionally, there have been a couple of times my page has become non-responsive (not sure they are related but believe there is a high likelihood).
What are the steps one would take to track down the cause of this error in order to resolve it?
Hoping the SO community can help!
Thanks in advance.
Check to see if you have the 'atom-ternjs' package installed. I have it installed on Atom 1.8.0 on OS X 10.11.5 and am seeing this error quite often recently. Disable this plugin if you have it installed and see if the error goes away.
Not really a permanent solution, but I found if you "restart" the ternjs server the errors go away (at least for a little while)
Related
I started to use termux in my cellphone, and looking for information I find that I can install hydra in it.
However, when I use the comand
pkg install hydra
All I get is an error message as you can see in the title. I've tried to update and upgrade the system several times, but I'm still getting the same error.
So, I wonder... is there a chance that this library has another name? (I said it because I've seen other comments with the same error in other posts)
So please, can you help me to solve this?
Additionaly, I upload 2 pictures: the first one with the error message I get. The second one is some information that I think I might help (when I seach for that command 'hydra', it seems to be not found).
Thanks in advance.
As you can see here Hydra package has been removed from Termux repositories and no longer installable.
I am setting up an OSC receiver at the moment using node-red and node-red-contrib-osc on a Windows 10 machine (Node.js version 12.13.1, npm Version 6.12.1).
Unfortunately, I cannot deploy the flow, node-red throws the following error: "Flows stopped due to missing node types". The OSC plugin was installed using the "Manage pallette" button.
On the console there is the following information logged during installation process:
[info] node-red-contrib-osc : Syntax Error : Unexpected token ...
When I start Deploy, the following info is logged: [info] Waiting for missing types to be registered: - osc
I can reproduce the issue on two Windows 10 machines and on Raspbian, too.
There are some similar questions here on stackoverflow which I read, but no suggested solution worked for me.
I hope someone has a deeper knowledge than I have.
A syntax error reported against a node can mean either:
you are using too old a version of Node.js for the code in the module
there is some other error with the node
Given you are using Node 12, it is unlikely to be the first issue. I suggest you check the node's github issue list to see if there are any known issues in this area and if not, perhaps report what you are seeing there.
https://github.com/njh/node-red-contrib-osc
So before the question I wanna point out that the only thing I could find on this issue was on this stackoverflow question. This issue suggest that this was an issue with wappalyzer, and it was fixed in version 4.0.1. however I am using wappalyzer version 5.1.4 and is up to date with this.
I am building a web-app based on the MEAN-stack, everything worked as intended for a long time, until this error kept poping up in my google-chrome console:
Everytime i would click in my app header, and use my front-end routing to load up different components / modules this error appears, however I dont see any issue with what the web-app presents to me (it's not like I am missing data)
More details on the error:
I have no idea whats going on, or where this issue comes from.
This was due to a failing plugin.
Disable all plugins, and enable them one at a time to find failing chrome extensions.
In this case it was the wappalyzer extension.
I am using Atom as my editor.I also found a great package that opens up a terminal window inside Atom. However, when I open the terminal I get this error:
I notified the author of the package about this and he said that another program may be using winpty - possibly the antivirus. I am using Windows but don't have an antivirus.
Any suggestions on how I can troubleshoot this issue?
I tried troubleshooting using a myriad of ways but the package seems broken for quite a number of people as well. The only solution I found was to utilize a package that was forked from the original terminal-plus called platformio-atom-ide-terminal
It can be found here: https://github.com/platformio/platformio-atom-ide-terminal
I learnt about it here: https://github.com/jeremyramin/terminal-plus/issues/201
I am able to get up and running with nodejs by following the steps in this tutorial
http://blog.jetbrains.com/webide/2011/11/webstorm-your-node-app/
However, I am not able to load any modules while running through the ide. The debugger just blows up at the line
express = require("express");
Please note that I have all the modules installed locally(node_modules directory under root of project directory) and not globally.
FYI, I am able to run the same from the command prompt, just not through intellij.
Please note, I am using node 0.6.6. I am running on Ubuntu 11.10 x64.
Thanks
-Venu
I have a suggestion how you may proceed.
First let me describe the problem, then the workaround, then the proposal to get this addressed.
Problem
Blow up at require("express")
Reason
By default intellij will suspend upon any exception. See the breakpoint rule.
You got stuck at the exception.
The exception, in this case, is due to the fact that module.js is trying to resolve the "express". It actually forms different paths and filenames (see logic in module.js, starting line 159).
Because not all permutations of paths and filenames formed properly, exception is thrown at fs.statSync() fs.js 414 just because that path/filename does not exists.
Workaround
Turn off break at all exceptions when startup/loading modules. Turn it back on when your server is running.
Proposal
next iteration of node.js library handles package/module resolution more elegantly? Let me see if there's a bug being filed already.