I'm using Jenkins 2.190.2, and I have the NodeJS Plugin v. 1.3.4 installed.
I can see the "Provide Node & npm bin/folder to PATH" option, in my individual job configure pages. There's a "NodeJS Installation" dropdown, with one entry - "NodeJS v10.16.0".
But when I go to the Manage Jenkins/Configure System page, I'd expect to see a NodeJS section, where I could specify which NodeJS Installations I wanted available in Jenkins. And there's nothing there.
This is no NodeJS section in /configure.
I've uninstalled and reinstalled the NodeJS Plugin, and it's still not there.
Any ideas?
OK - just plain stupid.
Plugin configuration isn't in /configure, anymore, it's in /configureTools.
Related
So, to be clear, I'm not asking about the possibility of INSTALLING multiple versions of Node, or the capability of switching between multiple versions with something like nvm.
(The original nvm package for Mac/Linux has an "exec" command that lets you run a command under a particular version of node. I think this would be a solution--but the nvm for Windows package doesn't have that "exec" command.)
Context:
I have an Azure function app API that must run under Node 14.0.0 (a requirement of Azure Function Core Tools version ~3, which itself is a customer requirement).
I also have a basic React app (using Parcel bundler) that runs under Node 11.14.0. I can't update the Node version to 14.0.0 because of an error ("Cannot locate the bindings file...").
For testing purposes, I need to run both simultaneously, so I can hit my API with my React app.
I have tried starting my API under Node 14.0.0, then using nvm to switch to 11.14.0 to run the React app, but it causes the API to fail with an "unsupported Node version" error. I haven't tried the converse approach because this error (along with the UAC prompt) tells me that the Node version in use is global.
Does anyone have any ideas of how to run two versions of Node on Windows? Or can anyone suggest another practical work-around?
Thanks in advance.
On setup nodejs app in the cpanel menu, there are so many version choice.
But when I login using ssh, the shown version is v8.17.0. How to change to 12 or later?
First you need to create nodejs application on your cpanel then the NPM binary executable will be created on /home/yourcpanelusername/nodevenv/yourprojectname/12/bin/. So just use it, example:
~/nodevenv/yourprojectname/12/bin/npm install
or if using node:
~/nodevenv/yourprojectname/12/bin/node index.js
I'm kinda new to strapi. actually this the first time to try it. so i followed the documentation and was able to get the first page to work but admin page always go blank. sadly i don't know nodeJs or react so I'm not sure about what to do in here but seems there's something wrong with the permissions please check the attached image.
i've tried
npm install in the project root directory.
npm run setup in the project root directory.
as mentioned in this issue on github but it want's useful
I'm using
strapi 3 alpha
nodeJs 11
npm 6+
mariaDB 10.1
windows 10 64bit
I suggest you to clean the database your use. And when it's done, restart your Strapi server. It will re-create all table needed by Strapi.
So simply, I checked strapi website to find out that version 3 is out of the alpha status and then I installed the newer version and tried to use it and it did work so seems some bug was in the alpha edition which strapi team has fixed by themselves
I had a similar issue after setting up SSL on Digital Ocean one-click. I just ran npm run build. I did not do anything with the database.
Just installed the latest Domino 10.0.1 Server on my linux machine and also installed and configured the latest proton package. As far as I can tell it's all running fine.
Next I plan to try my first Node-RED flow using the new Domino10 nodes. So I installed the 'node-red-contrib-dominodb' palette.
Finally tried my first very simple flow trying to query node-demo.nsf as it's described here. From what I read there I assumed that it's sufficient to install the palette, but that obviously is not the case:
as soon as I hit 'Deploy' I receive this error:
Error: Cannot find module '#domino/domino-db'
So I thought that I maybe still have to do a global install in node.js using
npm install -g <package-path>/domino-domino-db-1.1.0.tgz
This indeed created a local #domino/domino-db module inside my node.js npm\node_modules folder. But obviously my node-red environment doesn't know about it.
Question is: how do I register / install that npm package for my local node-red environment?
IBM's instructions (https://flows.nodered.org/node/node-red-contrib-dominodb#Installation)
Say to go view this guide(https://github.com/stefanopog/node-red-contrib-dominodb/blob/master/docs/Using%20the%20new%20Domino%20V10%20NodeRED%20nodes%202.pdf) for installing the domino-db module.
The link is broken, here's an old copy: https://github.com/stefanopog/node-red-contrib-dominodb/blob/a723ef88498c5bfa243abd956a7cc697f0a42610/docs/Using%20the%20new%20Domino%20V10%20NodeRED%20nodes%202.pdf
I believe the section you want is called "Import the tarball". The steps before that require you to unpack and then re-pack the module... which is unnecessary. Just use the tgz that was in the AppDev Pack to begin with.
I'm trying to install redbot in Node-RED, on IBM Bluemix. As suggested here, I'm using Manage palette to install it. I can find it in 'install' tab by typing chatbot. I click on install and then a pop up appears saying:
Before installing, please read the node's documentation. Some nodes
have dependencies that cannot be automatically resolved and can
require a restart of Node-RED.
I click on install again, and after loading a little bit, it shows this message:
Failed to install: node-red-contrib-chatbot Error: install failed
Check log for more information
And the debug tab shows this error message:
Error: Command failed: npm install --production
node-red-contrib-chatbot
I tried to install dependences listed here following the same procedure described in this post, but some of them can't be found from Manage palette. I also tried restarting Node-red but without success.
Is there any alternative? How should I install this properly?
You can only install Node-RED nodes via the manage palette system, not the underlying npm nodes.
The best way to install Node-RED nodes that won't install cleanly via the manage palette option is to edit the Node-RED package.json The easiest way to do this is to go to the Overview page for the application console page in Bluemix. From here click "Edit Code". From here you want to edit the package.json to include node-red-contrib-chatbot in the dependencies section.
"dependencies": {
"node-red-contrib-chatbot": "0.7.1",
...
},
Once you've made the changes you will need to commit and push the changes, this should restart Node-RED and as part of this the node should be installed.
What hardililb says but if the issue is with all nodes - i.e. you cannot add any node, not even a simple one like random, via the Manage Palette, you can fix that. Edit bluemix_settings.js and add:
var fs = require("fs");
Then after the var settings= section (not in it, after it), add:
// Ensure userDir exists
fs.mkdirSync(settings.userDir);
fs.mkdirSync(path.join(settings.userDir,"node_modules"));
Commit and Push.