I am getting error below after I tried to start node.js. Does anyone know the possible solution to the error below. I haven't used node.js at all. Please help!
http://i.stack.imgur.com/eri49.png
If you open the terminal as administrator before running the command the issue should be resolved
Related
I just started mobile automation testing and I'm trying to write tests for android on Android Studio with Appium, however I think I just did something wrong in configuration process. I was getting some other errors and these are the things I've done so far.
set ANDROID_HOME path
set JAVA_HOME path
updated node version
After doing these I've started appium server and tried again. I was able to communicate with the emulator but something is still off.
run command
appium-doctor and flutter doctor seems fine though.
appium-doctor
flutter doctor
And this is the exact error message I get.
this
Any help is appreciated. Thanks in advance.
I solved the case a while ago, thought could help someone. The problem was the first config I copied from another how-to source. It was trying to use appium-flutter-driver and I assume therefore there was a code snippet like this:
'appium:automationName': 'Flutter'
Which wasn't working because I was trying to run it with appium-flutter-finder. I don't exactly know what happened there but when I looket it up from appium's guide and did the default config they gave there the problem is gone. Which is:
'appium:automationName': 'Appium'
I'm trying to install the node.js project and run
npm install
and got the error
../src/main.cc:137:89: error: no matching function for call to 'v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)'
what is wrong with the project?
the full error is here https://paste.ubuntu.com/p/hJGDfdrKB2/
It looks like the package you are using doesn't support the version of Node you are running. Try running it under Node v8 and see if that corrects the problem. If it does let the package maintainer know it needs updating.
Plasma
downgrading to nodejs-10, worked for me.
Hope this will help.
Hello i am not really sure how to explain my problem or how to ask for help.
But am going to try it anyway lately when i create a react app it installs like normal.
But from the moment i use npm start i get this error (npm start error terminal).
Which says it has nothing wrong with node js/npm so i suspected it was something about the react app dependency that was wrong. When i downgrade to a older version of react scripts it works but the newest version 16.13.1 doesn't work even tho i use this version of react on my windows laptop. In case it helps to solve my issue here is the error log that npm generates (error log npm) i hope this helps to solve my issue
I have found the solution for my problem by setting the path value for system32.
You can do this by the following steps
Goto > Control Panel\System and Security\System\Advance system setting\Enviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.
After i have done these steps it seems to work
I am fairly new to React and am trying to run an example to get started with understanding how Twilio interfaces with React/Node. I am currently using the repo https://github.com/twilio/twilio-video.js, and am trying to run the test > framework > twilio-video-react, but when I npm install then npm start, the server starts, but throws the error:
Failed to compile
./src/App.js
Module not found: Can't resolve 'twilio-video'
I did `npm install twilio-video`, but still throwing error. What am I missing here? Can anyone else get this example started? I want a base example with Twilio Video working with React so I can learn from there, any other resources would help, thanks!
I tried these two examples as well, but they are outdated:
https://www.twilio.com/blog/2018/03/video-chat-react.html
https://www.twilio.com/blog/2016/03/building-a-react-powered-video-chat.html
Okay, got an example up and running with a little fudging.
I followed this example: https://www.twilio.com/blog/2018/03/video-chat-react.html
But there were a few old libraries that were causing errors.
Posted a working version on my Github linked here.
I recently started getting an error in my terminal when I start nodemon on my server.js file within my directory. Here is a picture below
Here is the error.
dyld: lazy symbol binding failed: Symbol not found: _node_module_register
Referenced from: /Users/dan/nodeStuff/crm-test/node_modules/mongoose/node_modules/mongodb/node_modules/bson/build/Release/bson.node
Expected in: dynamic lookup
Not sure what the issue is. I did a brew update and also made sure my port was correct.
For anyone else who stumbles by this problem, I had the same issue when trying to start my server with nodemon.
For me, the problem was I was still using an older version of node with nvm. I switched back to the version appropriate for my application and problem solved!
Did you try running node server.js?
Maybe it's not nodemon.
I've looked around and I did a npm rebuild which helped. When I start nodemon server.js or node server.js it tells me that one of the packages I was using is depreciated, I'm guessing that's what threw the error. Not sure why body-parser is depreciated.