I've just set up a Jenkins Server Cartridge from Openshift and I have a problem with npm due to the old version installed on the server (1.1.37).
Openshift doesn't allow us to root on the server so I can't update node/npm by the classic way.
I just had to scour the internet for a solution unsuccessfully so I figured someone may have a solution here.
edit:
The only answer from Openshift support service was: That is currently the version of npm that we support on our servers.
Related
I need help, currently I have developed on my computer with node js and git a gis application using openlayers . Now I try to install it on hosting in cpanel but I can't. Please help me because I've been trying for several days and I can't. I couldn't find a complete tutorial on how to install openlayers. I mention that I am new in this field.
I created an app with nodeJS in Cpanel, after i installed GIT with repository. On openlayers website, i followed the steps with npm create ol-app my-app, cd my-app, npm start. After this all i see when i acces the webpage is tha message from NodeJS "It works! NodeJS 16.17.1".
I am going to deploy Typescript(React) app on the Dreamhost.
But I don't know how to do that.
I can connect by SSH to the server.
Should I install npm by SSH then run that?
I saw an option about passenger on the Dreamhost server.
If I select this check box, then message shows requires VPS or dedicated server running a recent OS version.
But I don't know at all about how to do this. I have been using Dreamhost for only few months.
Please help me.
What requires a VPS or Dedicated server, is the RVM module:
Regarding your question: Node.js is not installed by default on newer DreamHost servers. You must manually install a custom version under your server's username.
Once installed, npm is also installed and you'll be able to run the commands below.
View the following article for instructions on how to install a custom version of Node.js.
Installing a custom version of NVM and Node.js
A project I am on has a Jenkins server to which I don't have remote access.
The server admin has installed npm 5.8 using npm install -g npm.
Executing npm -v reports a version of 5.8.
However, during the Jenkins build process, npm -v reports a version of 5.6 which is the version that shipped with the installed version of NodeJS.
Can someone assist me in what I should be asking the admin to change?
The admin should be able to install the Jenkins NodeJS Plugin which allows you to handle several different installations (in different versions) of NodeJS. This way you can address the version of NodeJS & npm you want to use from the Job configuration, as the correct folder is temporarily added to the PATH variable.
There is a walkthrough guide on the wiki page of the plugin.
Following steps will help you:
If it is windows machine, you better to restart the node after you install anything. Then only Jenkins can get the updated environment variables.
Verify the Environment variable pointed to correct version folder.
If you know the updated installed path then you can create local environment variable at job level using following command.
env.NODE_HOME =
"C:\Windows\system32\config\systemprofile\AppData\Roaming\npm"
I've created a webpart.
I'm using a Node.js, with npm, Yeoman and Gulp.
I installed a certificate with gulp trust-dev-cert, and I have this error on my page "This site can provide a secure connection", and the app isn't accessible.
This is my package.json
My node version is 8.9.1.
I tried to change the NODE_NO_HTTP2=1 environment variable , like this tutorial , but it doesn't work.
Do you have any idea to resolve my certificate problem ?
Thank you very much
Not sure why it isn't working after NODE_NO_HTTP2=1 changes.
I would suggest that you uninstall the current Node.js installation and reinstall the Node.js with the previous LTS version.
The previous Node.js version is v 6.12.
You can download it and install it on your machine and then run the gulp commands.
Link - Node.js v6.12.0
As mentioned here, currently only Node v6 is supported in SPFx
I have a CentOS 7 machine with mysql server and nginx. I installed nodejs with yum install nodejs and ghost-cli.
I wanted to install ghost with ghost-cli. but when I enter the ghost install commant I get this error:
✖ Checking system Node.js version
A SystemError occurred.
Message: The version of Ghost-CLI you are running was not installed with this version of Node.
This means there are likely two versions of Node running on your system, please ensure
that you are only running one global version of Node before continuing.
Debug Information:
Node Version: v6.11.1
Ghost-CLI Version: 1.1.0
Environment: production
Command: 'ghost install'
What's caused this error and how can I fix that? Thank you.
[Edited after Austin, the core contributor of Ghost-CLI, responded to
the issue]
I asked Austin, why he chose to not use local npm version?
He responded:
The reason for that is ghost creates a specific ghost user with which to run ghost. If you install nvm locally (e.g. in ~/.nvm), there is a very real (e.g. has happened several times) possibility that the created ghost user won't be able to run ghost because the home folder doesn't allow read permissions for everyone on the filesystem.
Going to close this issue for now - if more people have issues with this then we can reopen and figure out a better solution
Ok, so looks like you were able to resolve by running the installation as root but this is not something that I can do so I dug a little deeper into code that was pushed in the last couple of days to Ghost-CLI and my best guess is that this specific commit fix nvm -- ea30015 is causing the permission issue.
I have created an issue #447 with Ghost-CLI project to see if they can confirm it as well.