-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update nodejsVersion to >18.x or higher for support of npm >10.x #143
Comments
What ist the usecase of running npm packages inside of FHEM container instead of using a seperate container? |
Hi @sidey79 , nothing from my side. It is only annoying to see the FHEM system showing a red icon for not being up-to-date. Therefore I was trying to find a solution by getting the latest versions into the system. Cheers Volker |
The solution i recommend is using the minimal Image : ghcr.io/fhem/fhem-minimal-docker:3.3.1-buster There ist no nodejs installed, so no warning. |
@sidey79 will give it a try. Buster? Quite old bookworm is already out. Any chance on this? thx and cheers |
Bullseye ist also available, but bookworm isn't finished today: docker pull ghcr.io/fhem/fhem-minimal-docker:3.3.1-bullseye Those images are updated at regular base. |
The latest bullseye image |
Hi @git-developer , just confirmed by updating my system. Thx a lot for your efforts. Will mark this as resolved. |
Using the latest provided version of dockerized FHEM there are issues updating npm inside of docker to 10.x. The requirements therefore are requesting nodejsVersion >18.x instead of the provided version 16.20.2.
What else is needed from my side?
Thanks in advance and best regards
Volker
The text was updated successfully, but these errors were encountered: