unable to update / install

[dibadodo]

I was running th telegram bot for a lot of time. Today i trying to install the update. The install remove the existing version but is unable install the new version. Install log: 2022-02-11T22:25:15.246Z installieren : node-red-contrib-telegrambot 11.2.3

2022-02-11T22:25:15.273Z npm install --no-package-lock --global-style --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-telegrambot@11.2.3 2022-02-11T22:25:24.479Z [out] 2022-02-11T22:25:24.479Z [out] up to date in 8s 2022-02-11T22:25:24.575Z rc=0

I running node-red as redmatic inside a RaspberryMatic on Raspi3

Would be nice when i can get the old version to get it working again if the new version not running on my environment.

Greetings

[jbrown123]

I just attempted to install from scratch (no previous version). I got an error as well.

I'm running on an OrangePi with Node-Red v1.1.3.

Install log

2022-02-11T22:32:29.839Z Install : node-red-contrib-telegrambot 11.2.3

2022-02-11T22:32:28.630Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-telegrambot@11.2.3
2022-02-11T22:33:08.517Z [err] npm
2022-02-11T22:33:08.518Z [err]  WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-02-11T22:33:47.852Z [out] + node-red-contrib-telegrambot@11.2.3
2022-02-11T22:33:47.852Z [out] added 39 packages from 72 contributors in 72.417s
2022-02-11T22:33:47.981Z rc=0

[windkh]

I guess node red checks for the minimum supported version in package.json. maybe it is better to remove these properties. The deprecation warning can be ignored btw

[dibadodo]

You mean remove this properties inside node red or on the package side? When on side of node red - Where and How?

[dibadodo]

Please can you send me the old version to get it working again? Because of missing nodes the entire flows are disabled. :( I dont want to delete all telegram nodes...

Thank you

[windkh]

You can download all releases from this repo under Releases on the right pane

[jbrown123]

The deprecation warning can be ignored btw

FYI: I used the NR palette manager. The deprecated warning causes it to not install your package.

[windkh]

Hm? This message is there for ages… are you sure?..

[dibadodo]

You can download all releases from this repo under Releases on the right pane

I see under release only source code files as tar or zip. Are you sure I can upload them directly in node red?

[windkh]

You can simply replace the folder inside node red with those files… it should be even enough to just copy the two files 99-telegrambot.js and .html…. As an alternativ you can install the package into nodered via command line Npm install …

[jbrown123]

Hm? This message is there for ages… are you sure?..

The install failed and this was the entire log. Note that they are marked as errors, not warnings. Just tried it again with the same results.

This is the error message I get:

Here are the logs:

-----------------------------------------------------------
2022-02-11T22:32:29.839Z Install : node-red-contrib-telegrambot 11.2.3

2022-02-11T22:32:28.630Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-telegrambot@11.2.3
2022-02-11T22:33:08.517Z [err] npm
2022-02-11T22:33:08.518Z [err]  WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-02-11T22:33:47.852Z [out] + node-red-contrib-telegrambot@11.2.3
2022-02-11T22:33:47.852Z [out] added 39 packages from 72 contributors in 72.417s
2022-02-11T22:33:47.981Z rc=0

-----------------------------------------------------------
2022-02-12T21:08:22.185Z Install : node-red-contrib-telegrambot 11.2.3

2022-02-12T21:08:20.783Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-telegrambot@11.2.3
2022-02-12T21:08:58.641Z [err] npm
2022-02-12T21:08:58.643Z [err]  WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-02-12T21:09:27.726Z [out] + node-red-contrib-telegrambot@11.2.3
2022-02-12T21:09:27.726Z [out] updated 1 package in 61.058s
2022-02-12T21:09:27.841Z rc=0

[dibadodo]

Replacing the folder does not work, I think the old package was uninstalled during the update process. I can use directly the source files? Sorry, I'm not a developer - I'm just a user.... ;)

[windkh]

Go to the node red folder with the subfolder node_modules and type in via command line npm install node-red-contrib-telegrambot

[colinl]

I don't see any errors in the install logs shown. What exactly is the problem that people are having here?

[colinl]

For anyone who does want to install an old version then go into your .node-red folder (or wherever the flows are located) and run npm install node-red-contrib-telegrambot@a.b.c where a.b.c is the version you want.

[dibadodo]

sorry, direct install with npm seems doesn't work on Redmatic on Rapsberrymatic. I can upload a tar.gz file or i install direct from repository but only from gui

[colinl]

In what way does the npm install not work? What does it say when you try to do it?

[dibadodo]

npm via cli don't work - that is the output:

/usr/lib/node_modules# npm install node-red-contrib-telegrambot npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN checkPermissions Missing write access to /usr/lib/node_modules npm ERR! code EROFS npm ERR! syscall access npm ERR! path /usr/lib/node_modules npm ERR! errno -30 npm ERR! rofs EROFS: read-only file system, access '/usr/lib/node_modules' npm ERR! rofs Often virtualized file systems, or other file systems npm ERR! rofs that don't support symlinks, give this error.

npm ERR! A complete log of this run can be found in: npm ERR! /tmp/npm-cache/_logs/2022-02-12T21_43_44_177Z-debug.log

I'm logged in as root.

[colinl]

You are in the wrong folder. You must be in the folder where your flows file is (usually the user's .node-red folder).

[colinl]

And don't run it as root. Run it as the user that runs node-red (unless that is root which is almost always a bad idea).

[dibadodo]

I have no idea which path is the right and i don't know which user is used - as explained on my first post, this is a raspberrymatic installation and redmatic is a plugin on this - Raspberrymatic is installed as a image and will only accessed via browser - redmatic will be installed via upload a file from gui - that is all - so i don't know where and on which user is each service running - because of this i don't want to install some thing via cli and outside the normal system - but i was looking how to use npm on this system - that is the output:

/usr/local/addons/redmatic/var# npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-telegrambot@11.2.3

up to date, audited 589 packages in 8s

57 packages are looking for funding run npm fund for details

8 vulnerabilities (3 low, 2 moderate, 3 high)

To address issues that do not require attention, run: npm audit fix

To address all issues possible (including breaking changes), run: npm audit fix --force

Some issues need review, and may require choosing a different dependency.

Run npm audit for details.

The package is not available on redmatic, i have restarted the redmatic but is still not available - i got still the the message:

Flows were stopped due to missing nodetypes.

The package is not show as installed on package manager.

[dibadodo]

I was able to remove the package now - i have reinstalled the old version 10.4.1 - that ist the output

npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-telegrambot@10.4.1 npm WARN tarball tarball data for xmlbuilder@https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5 (sha1-s3HoCc/cD2GzELUrYF1Ds5h/FVk=) seems to be corrupted. Trying again. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

I restarted redmatic / node-red and it was successful running The i have uninstalled the package and reinstalled wit actual version - that ist the output

npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-telegrambot npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

added 125 packages, removed 3 packages, changed 229 packages, and audited 596 packages in 4m

I restarted the system but it don't work. I get the error message again : Flows were stopped due to missing nodetypes. I see no reason why new version is not running.

with npm list the package shows me as installed with version 11.2.3 +-- node-red-contrib-telegrambot@11.2.3

good night

[TotallyInformation]

I would suggest raising this issue in the redmatic or raspberrymatic forum since the issues seem to be caused by those. It doesn't appear to happen on Node-RED itself.

However, there are several outdated dependencies in this module that could do with being updated (not sure if they are deep or direct dependencies though).

[dibadodo]

I think you are right - redmatic use a old version of node-red - maybe that is the main reason But it would be nice to know what is the reason that the last version of 10.x is working and the version of 11.x not. I will open a issue on redmatic - Thank you for your time

[jbrown123]

I am NOT using redmatic. I'm using a standard node red running on an Orange Pi. I haven't tried a direct npm install, but I am seeing failure (log above) using the node red palette manager.

Other packages install correctly using the palette manager

[TotallyInformation]

Anything might change between major versions of node.js. At the very least, you need to do an npm rebuild on the userDir folder to recompile any C++ libraries, this is a common issue.

On the OrangePi, please try a direct install as that may give more information. What version of node.js, npm and node-red do you have on the orangepi and what OS version?

[windkh]

I released 11.2.4 without the version info. Please check if this works now... https://github.com/windkh/node-red-contrib-telegrambot/releases/tag/V11.2.4

[colinl]

Why didn't you just revert the previous change? Then you would know it would be ok.

[windkh]

Why didn't you just revert the previous change? Then you would know it would be ok.

… well, because with that change the problems started…. I just wanted to have a release that does not cause even more troubles.

[colinl]

I thought that 11.2.2 was ok. Which was the first version that caused problems?

[windkh]

11.2.0 was the last known good one

[colinl]

OK, that was not clear to me as this issue is specifically about 11.2.3 The reason for the problems in this issue are the node-red version in the engines directive. I can't comment on any other issues with previous versions as I don't know what they are.

[dibadodo]

Hi,

I can confirm this. Version 11.2.2 still works, 11.2.3 has the described problems - the new version 11.2.4 works again. Great Many thanks for your effort

I think we can close this call.

Regards

[dibadodo]

Sorry, the new package damaged my repository. After installation i have tried to show the installed packages with npm list. I got a lot off error messages like this: npm list npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it! npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

followed from

+-- node-red-contrib-combine@1.8.1 +-- UNMET DEPENDENCY node-red-contrib-deconz@2.3.3 | +-- UNMET DEPENDENCY @node-red/util@2.1.1 | | +-- UNMET DEPENDENCY fs-extra@10.0.0 | | | +-- UNMET DEPENDENCY graceful-fs@4.2.8 | | | +-- UNMET DEPENDENCY jsonfile@6.1.0 | | | | +-- UNMET DEPENDENCY graceful-fs@4.2.8 | | | | -- UNMET DEPENDENCY universalify@2.0.0 | | |-- UNMET DEPENDENCY universalify@2.0.0 | | +-- UNMET DEPENDENCY i18next@21.3.1 | | | -- UNMET DEPENDENCY @babel/runtime@7.15.4 | | |-- UNMET DEPENDENCY regenerator-runtime@0.13.9 | | +-- UNMET DEPENDENCY json-stringify-safe@5.0.1 | | +-- UNMET DEPENDENCY jsonata@1.8.5

and then: npm ERR! missing: node-red-contrib-deconz@2.3.3, required by node-red-project@0.0.1 npm ERR! missing: node-red-contrib-hikvision-ultimate@1.0.60, required by node-red-project@0.0.1 npm ERR! missing: node-red-contrib-telegrambot-home@0.7.0, required by node-red-project@0.0.1 npm ERR! missing: node-red-dashboard@3.1.5, required by node-red-project@0.0.1 npm ERR! missing: node-red-node-email@1.14.0, required by node-red-project@0.0.1 npm ERR! missing: node-red-node-tail@0.3.2, required by node-red-project@0.0.1 npm ERR! missing: node-red-contrib-telegrambot@~11.2.2, required by node-red-project@0.0.1 npm ERR! invalid: xmlbuilder@0.4.2 /usr/local/addons/redmatic/var/node_modules/node-red-contrib-ccu/node_modules/homematic-xmlrpc/node_modules/xmlbuilder npm ERR! missing: ws@8.2.3, required by node-red-contrib-deconz@2.3.3 npm ERR! missing: @node-red/util@2.1.1, required by node-red-contrib-deconz@2.3.3 npm ERR! missing: compare-versions@3.6.0, required by node-red-contrib-deconz@2.3.3 npm ERR! missing: dot-prop@6.0.1, required by node-red-contrib-deconz@2.3.3 npm ERR! missing: got@11.8.2, required by node-red-contrib-deconz@2.3.3 npm ERR! missing: set-interval-async@2.0.3, required by node-red-contrib-deconz@2.3.3 npm ERR! peer dep missing: jquery@1.9.1 - 3, required by multiple-select@1.5.2 npm ERR! extraneous: ws@8.2.3 /usr/local/addons/redmatic/var/node_modules/node-red-contrib-deconz/node_modules/ws npm ERR! missing: fs-extra@10.0.0, required by @node-red/util@2.1.1

Uninstalling of the new Package fails with this message:

npm uninstall node-red-contrib-telegrambot npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it! npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN multiple-select@1.5.2 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself. npm WARN node-red-project@0.0.1 No repository field. npm WARN node-red-project@0.0.1 No license field.

added 4 packages from 13 contributors, removed 126 packages, updated 279 packages and audited 473 packages in 212.023s

39 packages are looking for funding run npm fund for details

found 4 vulnerabilities (1 low, 1 moderate, 2 high) run npm audit fix to fix them, or npm audit for details

┌───────────────────────────────────────────────────┐ │ npm update check failed │ │ Try running with sudo or get access │ │ to the local update config store via │ │ sudo chown -R $USER:$(id -gn $USER) /root/.config │ └───────────────────────────────────────────────────┘

[colinl]

@dibadodo what do these commands show node -v npm -v

[dibadodo]

node -v v12.22.7

npm -v 6.14.15

[colinl]

What does this command give? npm install Running in the .node-red folder obviously

[jbrown123]

I'm still getting the same exact same error via Node-Red palette manager with 11.2.4 as with 11.2.3. Same log entries as well.

2022-02-14T21:15:05.212Z Install : node-red-contrib-telegrambot 11.2.4

2022-02-14T21:15:04.305Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-telegrambot@11.2.4
2022-02-14T21:15:40.346Z [err] npm
2022-02-14T21:15:40.347Z [err]  WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-02-14T21:16:09.280Z [out] + node-red-contrib-telegrambot@11.2.4
2022-02-14T21:16:09.280Z [out] updated 1 package in 59.944s
2022-02-14T21:16:09.366Z rc=0

Here's my environment

Node Red 
v1.1.3

node -v
v12.20.1

npm -v
6.14.10

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.7 LTS
Release:        16.04
Codename:       xenial

uname -r
3.4.113-sun8i

cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepione
BOARD_NAME="Orange Pi One"
BOARDFAMILY=sun8i
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=76ac54aa
VERSION=5.90
LINUXFAMILY=sun8i
BRANCH=default
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=zImage

[colinl]

@jbrown123 there are no errors there. It says it has installed version 11.2.4

2022-02-14T21:16:09.280Z [out] + node-red-contrib-telegrambot@11.2.4
2022-02-14T21:16:09.280Z [out] updated 1 package in 59.944s

[windkh]

@jbrown123 what happens after you restart node-red?

[dibadodo]

@colinl

npm install npm WARN multiple-select@1.5.2 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself. npm WARN node-red-project@0.0.1 No repository field. npm WARN node-red-project@0.0.1 No license field.

audited 478 packages in 18.17s

57 packages are looking for funding run npm fund for details

found 4 vulnerabilities (1 low, 1 moderate, 2 high) run npm audit fix to fix them, or npm audit for details ^C ┌───────────────────────────────────────────────────┐ │ npm update check failed │ │ Try running with sudo or get access │ │ to the local update config store via │ │ sudo chown -R $USER:$(id -gn $USER) /root/.config │ └───────────────────────────────────────────────────┘

[jbrown123]

The palette manager gives an error and says it did NOT install.

After install, telegrambot does not appear in the nodes list

It still shows up in the list of available packages to be installed.

It does, however, show up as an installed package when you do an npm list in the .node-red folder

~/.node-red$ npm list --depth=0
node-red-project@0.0.1 /home/james/.node-red
├── node-red-contrib-arp@0.0.2
├── node-red-contrib-bigtimer@2.7.5
├── node-red-contrib-castv2@4.1.2
├── node-red-contrib-config@1.2.1
├── node-red-contrib-debounce@0.0.2
├── node-red-contrib-fs-ops@1.6.0
├── node-red-contrib-functionx@1.0.2
├── node-red-contrib-light-scheduler@0.0.17
├── node-red-contrib-npm@1.0.2
├── node-red-contrib-persistent-fsm@1.1.0
├── node-red-contrib-play-audio@2.5.0
├── node-red-contrib-telegrambot@11.2.4        <======================
├── node-red-contrib-time-range-switch@1.0.1
├── node-red-contrib-tplink@1.0.0
├── node-red-contrib-ui-led@0.4.9
├── node-red-dashboard@2.29.0
├── node-red-node-email@1.12.1
├── node-red-node-google@0.2.2
├── node-red-node-pi-gpio@1.2.3
├── node-red-node-ping@0.3.1
├── node-red-node-random@0.4.0
├── node-red-node-rbe@0.5.0
├── node-red-node-serialport@0.14.0
├── node-red-node-smooth@0.1.2
└── node-red-node-tail@0.3.1

[windkh]

This is realy weird

[jbrown123]

@jbrown123 what happens after you restart node-red?

Restarting node-red causes telegram to appear in the list (as expected, since it was listed as an installed module).

I don't know if you want to keep this here, or start a new issue of "doesn't report that it installed correctly via palette manager".

[windkh]

Well I do not have any idea what is going on here nor do I see anything I could do about it…

[jbrown123]

Clearly something is unhappy in the palette manager. Does it not do this when you attempt to install via the palette manager?

[colinl]

What did you see when you clicked View Log in the popup error message?

[jbrown123]

Exactly what I posted previously in https://github.com/windkh/node-red-contrib-telegrambot/issues/235#issuecomment-1039569605

2022-02-14T21:15:05.212Z Install : node-red-contrib-telegrambot 11.2.4

2022-02-14T21:15:04.305Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-telegrambot@11.2.4
2022-02-14T21:15:40.346Z [err] npm
2022-02-14T21:15:40.347Z [err]  WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-02-14T21:16:09.280Z [out] + node-red-contrib-telegrambot@11.2.4
2022-02-14T21:16:09.280Z [out] updated 1 package in 59.944s
2022-02-14T21:16:09.366Z rc=0

[jbrown123]

If you clear the browser cache (via the browser menus) and refresh the page, does it still not show up as installed in the palette manager?

Unfortunately I've restarted node-red now and it does show in the palette after restart (as shown above).

I've never had this problem before with any other modules (as you can see from above, I have several installed).

If it's useful, I can uninstall the module, restart node-red and repeat the process. I don't know if I will get the error again. Presumably I would.

[colinl]

If you installed via npm and then tried to install via the palette manager, without re-starting node-red first then that could have confused it temporarily. You must restart node-red after changing the modules behind its back before doing anything else. Yes, you could try removing it and then re-installing via the palette manager again. Why are you using an ancient version of node-red?

[jbrown123]

If you installed via npm and then tried to install via the palette manager,

I have ONLY attempted install via NR palette manager. It clearly installed 11.2.4 even though it said it failed.

Why are you using an ancient version of node-red?

I installed a couple of years ago and just haven't updated NR. The "if it ain't broke don't fix it" philosophy.