Error in installing openVPN module in node js - javascript

I am trying to connect Sophos VPN using nodejs. For this I am referring below link
https://github.com/luigiplr/node-openvpn
So while executing npm install node-openvpn --save command I am getting error. Can anyone please help me with this issue? Below is the screenshot of error
enter image description here

Clean your cache and try again:
npm cache clean --force
npm install node-openvpn --save

Related

Unable to use typescript with expo - "It looks like you're trying to use TypeScript but don't have the required dependencies installed"

I am receiving an error while trying to use Typescript with my existing expo project.
While following the docs, I created a tsconfig.json file in the project root.
When running expo start, I am prompted to install the typescript dependencies. However, after these are successfully installed (tick message appears in console: √ Installed typescript#~4.3.5, #types/react#~17.0.21, #types/react-native#~0.67.6), I receive the following error:
It looks like you're trying to use TypeScript but don't have the required dependencies installed.
Please install #types/react by running:
yarn add --dev #types/react#~17.0.21
If you're not using TypeScript, please remove the TypeScript files from your project and delete the tsconfig.json.
error Command failed with exit code 1.
After following the instructions and running the yarn add .... command, I keep seeing the same error message.
I have tried deleting the node_modules folder and package-lock.json file to no avail. I have also tried following this answer.
Any assistance would be appreciated, thank you.
Seems to be a bug. It works if I install #types/react on the specific version that Expo requests (17.0.21).
yarn add --dev #types/react#17.0.21
Just re-install expo-cli npm install -g expo-cli.
I don't know which of the following worked, but I ran the following commands and the problem went away.
sudo npm install -g expo-cli
sudo npm install -g #types/react
sudo npm install -g #types/react-native
sudo npm install -g typescript
yarn add expo-cli
solved for me.
I had the same issue. I resolved it by :
1- delete the node_modules.
2- update expo to the latest version using npm i -g expo-cli
hope this will help someone
if you installed #types/react remove that from your dev dependencies

Unable to install a package on Next JS

I've been trying to install styled-components on Next JS by entering npm install --save styled-components but it keeps giving me this error...
npm ERR! Unexpected end of JSON input while parsing near '...ry.npmjs.org/fork-ts-'
Please can anyone help me out?
Try to clean the npm cache running the following command:
npm cache clean --force

npm installation in command prompt

After setting new windows in my laptop,i am trying to install npm in command prompt.But i am facing an error which picture is given in below.Would anybody help me out?
If you don't specify a package to install (like npm install -g nodemon) npm will try to install all packages from the current package.json file. If there is non, npm will throw this error.
Npm is already installed. That is why the error message is not Command not found.
The specific command you issued npm install -g attempts to use npm to install the package in the current directory globally.
Leaving the point that installing packages globally is a bad idea aside, this is failing because you are running the command in a directory that does not contain a package. It is your home directory, not one containing a package.json file.
If you are trying to install npm(node package manager) do it by downloading it from here: https://www.npmjs.com/get-npm, then you are good to go.
The command you are actually giving is to install a package using npm(check https://docs.npmjs.com/cli/install).
Thats why the error shows could not install from "" as you have not specified any package to install.

Getting error Cannot find module 'cryptile' while installing express js

I am new to node js and facing issue in installing express js. Please help in fixing the issue and install express js.
Now when i tried to install cryptiles module using the command "npm install cryptiles" i am getting the same error.
Just run npm install cryptiles then re-run your previous command
or if you don't want then go to your packages.json file and remove the dependency...
UPDATE :
Seems this package isn't supported anymore ..
To see yourself install globally:
npm install -g cryptiles
then install try to install in source destination
npm install cryptiles
You should get the following message:
npm WARN install Couldn't install optional dependency: Unsupported

Bower - EPERM, unlink error

I'm encountering the below error stack trace, while I try to install "jQuery" using Bower. Can someone offer some help?
C:\study\meanApp>bower install jquery --save
bower not-cached git://github.com/jquery/jquery.git#*
bower resolve git://github.com/jquery/jquery.git#*
bower download https://github.com/jquery/jquery/archive/2.1.1.tar.gz
bower retry Download of https://github.com/jquery/jquery/archive/2.1.1.t
ar.gz failed, trying with git..
bower EPERM EPERM, unlink 'C:\Users\UserZ\AppData\Local\Temp\AUserZ\bower\jquery-8680-AaJIqU\archive.tar.gz'
Stack trace:
Error: EPERM, unlink 'C:\Users\UserZ\AppData\Local\Temp\A-UserZ\bower\jqu
ery-8680-AaJIqU\archive.tar.gz'
Console trace:
Trace
at StandardRenderer.error (C:\Users\UserZ\AppData\Roaming\npm\node_module
s\bower\lib\renderers\StandardRenderer.js:72:17)
at Logger.<anonymous> (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bo
wer\bin\bower:110:22)
at Logger.EventEmitter.emit (events.js:95:17)
at Logger.emit (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\nod
e_modules\bower-logger\lib\Logger.js:29:39)
at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\lib\commands\ind
ex.js:40:20
at _rejected (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_
modules\q\q.js:797:24)
at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_modules\q\q
.js:823:30
at Promise.when (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\no
de_modules\q\q.js:1035:31)
at Promise.promise.promiseDispatch (C:\Users\UserZ\AppData\Roaming\npm\no
de_modules\bower\node_modules\q\q.js:741:41)
at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_modules\q\q
.js:557:44
System info:
Bower version: 1.3.9
Node version: 0.10.18
OS: Windows_NT 6.1.7601 ia32
P.S: I've gone through the StackOverflow could find nothing related to my error, hence posting this question.
Thanks in advance,
Dave
Cleaning the cache resolved the error for me: npm cache clean
I got the same error "EPERM, unlink" but with a different archive.
Running these commands resolved the issue for me:
npm uninstall -g bower
npm update decompress-zip
npm install -g bower
This link is where I saw to use those commands: https://github.com/bower/bower/issues/798
It is the updating of the decompress-zip that has resolved the issue for others as well.
I got this error and ran the bower in verbose mode. And found the error as below:
bower error SELF_SIGNED_CERT_IN_CHAIN
To resolve this, add below line into .bowerrc created in your default home directory.
"strict-ssl": false
Try bower install again, it should work.
You could try the following sequence. It worked for me.
bower cache clean
npm uninstall -g bower
npm install -g bower
bower install jQuery#2.1.1
I had a similar problem and i resolved it pretty easily; I was trying to bower install while running a server from my machine. I disconnected the server and IDE (webstorm) and it worked.
i also got the same problem and i tried again all uninstalled everything then after i install again gitbash
command in gitbash
$ npm install -g bower // let it execute
once executed
again command
$ bower install bootstrap // let it execute
when executed you got
if want more then run more commands :)
e.g.
$ bower install script.js
Whenever I encounter this error, what I do is to clean the npm's cache,
npm cache clean
and if it doesn't work, I uninstall the concerned bower component, and install it again.
Uninstall your old node (it may be < 0.12.0)
And Install node version > v0.12.0 (In my case v0.12.7)
Then
npm update npm -g
And
bower install
I resolved it by running
bower cache clean

Categories