When I had 1.1.3 installed the following worked... npm list -g | grep '@types/node' Now this works... npm list | grep '@types/node' │ │ │ ├── @types/node@12.19.0 │ │ │ ├── @types/node@13.13.28 Just asking if this is expectation forward?

If I do a 'npm install' against the package.json... could that have moved Node somehow? I ran the official script to install 1.2.2, then npm install against my existing package.json... which I created from scratch as I populated 1.1.3. Wondering if Node could have moved some how? I just can't see…

Just asking if this is expectation forward? I"m not sure what we're meant to be seeing here? What version of node.js is this? What version of npm? could that have moved Node somehow What "Node" do you mean? node.js? Running npm install against your package.json file won't touch anything glob…

This sounds more like a misconception how npm works. I cannot say based on your post which commands you've ran and where. npm list lists packages installed under the current directory you are in. You're listing @types/node-red which is the package containing TypeScript types for Node-RED. Any packa…

@ristomatti So nothing changed with 1.2.2... Cool. Thanks for confirming. So I have a npm mystery again. It happens. I have a flow that checks for newer versions of Node, NR, npm, etc. It has been working well for some time. But today, something changed, throwing a wrench in my flow. One of …

[image] Nodi.Rubrum: I find... that the node-red-serialport module was not installed, yet it was clearly qualified in the package.json, under ~/.node-red/ on a new Pi image. So out of 40 odd modules installed, one was not? Not surprisingly and the likely explanation is here: [ima…

Yeah, and why @knolleary noted in another thread, npm rebuild is often required and recommended. Like I said, just when I think I have got npm figure out... curve ball!

[image] Nodi.Rubrum: I find... that the node-red-serialport module was not installed, yet it was clearly qualified in the package.json, under ~/.node-red/ on a new Pi image. Can you explain exactly what you mean by that please? I would not expect to see node-red at all in package.json if you …

The package.json was created via npm install of individual modules. I then copied the package.json to a new Pi OS install, i.e. /home/pi/.node-red/, where I had just run the NR install script (for 1.2.2). I then ran npm install. All the modules installed (or I should say any not already installed…

The reason I had to ask was because initially you said that you had node-red-serialport in package.json and that it didn't install it. If package.json had included that then it would not have been in the least surprising that it did not install as there is no node called that. It is node-red-node-…

I did not edit the json... you are correct, I mistyped the name of the package, should have checked the package name, in hindsight. You raise a good point, I should be using the lock file for strict standardization, you mentioned that you use the lock file some time ago, and I had yet to change my …

Node-RED

Node-RED Forum

So, with NR 1.2.x Node is not a global install?

General

Andrei 23 October 2020 00:54 6

Not surprisingly and the likely explanation is here:

Topic		Replies	Views
Cannot update Node-Red v1.0.6 General	21	2169	19 October 2020
Not having any luck updating General	100	3701	5 February 2019
Npm, versioning and palette manager confusions General	75	3160	26 April 2021
Upgrade problem: Node-RED is not yet fully installed General	73	12906	14 July 2020
Npm install issues? General	8	2707	11 September 2022

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

So, with NR 1.2.x Node is not a global install?

Related topics