MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    NPM problem "EBADENGINE" which I fail to solve

    Scheduled Pinned Locked Moved Solved Troubleshooting
    19 Posts 3 Posters 16.1k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I Offline
      Ix
      last edited by

      Hello everyone!

      Since I updated Kristjan Esperanto’s fork of the module "PublicTransportHafas to the newest version I can’t get it to run. When I use the command “npm ci” after “git pull” I just get the following error messages:

      error messages node.png

      Note that I tried and updated the version of node.js to the required version (at least I think I did. It does’t seem to work the way I tried).

      Is anyone here who has some experience troubleshooting such node problems? What am I missing? Please help, and Thank you in advance!

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @sdetweil
        last edited by

        @Ix the module author says this is a bug in the lint checker…

        do this, in the module folder

        npm i @stylistic/eslint-plugin@1.8.1
        

        then npm install

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        I 1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil @Ix
          last edited by

          @Ix says require 18.18.0 current 18.17.1

          so I would do

          node -v
          hash -r
          node -v 
          

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          I 1 Reply Last reply Reply Quote 0
          • I Offline
            Ix @sdetweil
            last edited by Ix

            Hello @sdetweil and thank you for your fast answer!

            I tried and pasted your commands in my terminal. Sadly, it didn’t work…
            Here’s what it says:

            mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ node -v
            hash -r
            node -v 
            v18.18.0
            v18.18.0
            mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ sudo npm ci
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@stylistic/eslint-plugin@2.1.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@stylistic/eslint-plugin-js@2.1.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: 'eslint-visitor-keys@4.0.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@stylistic/eslint-plugin-jsx@2.1.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/utils@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@stylistic/eslint-plugin-ts@2.1.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/utils@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/scope-manager@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/types@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/typescript-estree@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: '@typescript-eslint/visitor-keys@7.9.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || >=20.0.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: 'espree@10.0.1',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            npm warn EBADENGINE Unsupported engine {
            npm warn EBADENGINE   package: 'eslint-visitor-keys@4.0.0',
            npm warn EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
            npm warn EBADENGINE   current: { node: 'v18.17.1', npm: '10.7.0' }
            npm warn EBADENGINE }
            
            > mmm-publictransporthafas@2.1.1 prepare
            > [ -f node_modules/.bin/husky ] && husky || echo husky is not installed.
            
            
            added 436 packages, and audited 437 packages in 43s
            
            155 packages are looking for funding
              run `npm fund` for details
            
            found 0 vulnerabilities
            
            

            It’s as if it doesn’t recognize my used version of node…

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              MMRIZE @Ix
              last edited by MMRIZE

              @Ix
              Install recent nodejs.
              I don’t know how you have installed the current version of nodejs. So I cannot give you an exact advice.
              Generally I prefer to manage node version with nvm

              I S 2 Replies Last reply Reply Quote 0
              • I Offline
                Ix @MMRIZE
                last edited by

                @MMRIZE said in NPM problem "EBADENGINE" which I fail to solve:

                Install recent nodejs.
                I don’t know how you have installed the current version of nodejs. So I cannot give you an exact advice.

                Hey @MMRIZE 👋

                I used the following command:

                curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
                

                which I found here

                this is “nvm” isn’t it?

                1 Reply Last reply Reply Quote 0
                • S Offline
                  sdetweil @MMRIZE
                  last edited by sdetweil

                  @MMRIZE 1st line of 1st included message image shows his nvm command

                  says using 18.18.0

                  the npm ci says using 18.17.1

                  try npm i

                  I use n, which is a nodejs version of nvm

                  sudo mpn install n

                  n version
                  n list
                  n --help

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  I 2 Replies Last reply Reply Quote 0
                  • I Offline
                    Ix @sdetweil
                    last edited by

                    @sdetweil said in NPM problem "EBADENGINE" which I fail to solve:

                    try npm I

                    also tried this. same result :-/

                    1 Reply Last reply Reply Quote 0
                    • I Offline
                      Ix @sdetweil
                      last edited by

                      @sdetweil said in NPM problem "EBADENGINE" which I fail to solve:

                      I use n, which is a nodejs version of nvm

                      sudo mpn install n

                      n version
                      n list

                      I also tried this.
                      Here are the results:

                      mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ n list
                      node/22.2.0
                      mirror@raspberrypi:~/MagicMirror/modules/MMM-PublicTransportHafas $ n version
                      
                        Error: invalid version 'version'
                      
                      
                      
                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        sdetweil @Ix
                        last edited by sdetweil

                        @Ix version is the one you want to use

                        n 18

                        n 18.18

                        need sudo to change, as it write to /usr/local/bin which is protected
                        (as as nvm does)

                        see
                        n --help

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        I 1 Reply Last reply Reply Quote 0
                        • I Offline
                          Ix @sdetweil
                          last edited by

                          @sdetweil

                          I already tried and changed my used version to v18.18 via nvm (what obviously didn’t work)

                          Now I installed “n” and tried again with your method.
                          Here are the results:

                          mirror@raspberrypi:~/MagicMirror/modules $ sudo n 18.18
                            installing : node-v18.18.2
                                 mkdir : /usr/local/n/versions/node/18.18.2
                                 fetch : https://nodejs.org/dist/v18.18.2/node-v18.18.2-linux-arm64.tar.xz
                               copying : node/18.18.2
                          /usr/bin/n: Zeile 746: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden
                             installed :  (with npm 9.8.1)
                          

                          There is an error: “Datei oder Verzeichnis nicht gefunden” which translates into “File or directory not found” (Sry for my German OS 😅)

                          so there is another issue

                          S 1 Reply Last reply Reply Quote 0
                          • 1
                          • 2
                          • 1 / 2
                          • First post
                            Last post
                          Enjoying MagicMirror? Please consider a donation!
                          MagicMirror created by Michael Teeuw.
                          Forum managed by Sam, technical setup by Karsten.
                          This forum is using NodeBB as its core | Contributors
                          Contact | Privacy Policy