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.

    ./node_modules/.bin/electron js / electron.js Problem

    Scheduled Pinned Locked Moved Troubleshooting
    23 Posts 2 Posters 3.0k Views 2 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.
    • Y Offline
      youssef
      last edited by sdetweil

      Hello

      when I try to start mm she give me this error msg

      can anyone help me please !

      f860d263-f976-40d4-82e3-f9ffeaf6bab5-image.png

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

        @youssef is this a pi0?

        if so, remove the mm folder and use my script to do the install, see here

        https://github.com/sdetweil/MagicMirror_scripts

        Sam

        How to add modules

        learning how to use browser developers window for css changes

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

          @sdetweil thanks for your response

          it’s raspberry pi Desktop Version

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

            @youssef what processor is this on? I just fixed the install script for 32bit systems

            unamed -m
            output is i686

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            Y 2 Replies Last reply Reply Quote 0
            • Y Offline
              youssef @sdetweil
              last edited by

              @sdetweil said in ./node_modules/.bin/electron js / electron.js Problem:

              unamed -m

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

                @sdetweil thanks for your response again

                uname -m give me this result x86_64

                29f87250-a425-48eb-a5e4-0dea1465a8ff-image.png

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

                  @youssef interesting…

                  still suggest using my script…

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

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

                    @sdetweil thanks for responding

                    I try with your scrip they give the same error

                    44438cdb-08a0-4ef7-b041-9f27a041eff7-image.png

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

                      @youssef can u post ~/install.log
                      or send to my email, sdetweil at gmail

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

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

                        @sdetweil thanx for your response

                        install starting - Tue Mar 2 04:00:50 HST 2021
                        installing on x86_64 processor system
                        the os is Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster
                        Updating packages …
                        Get:1 http://security.debian.org buster/updates InRelease [65.4 kB] Hit:2 http://ftp.debian.org/debian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Get:4 http://packages.microsoft.com/repos/code stable InRelease [10.4 kB] Get:5 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB] Hit:6 https://deb.nodesource.com/node_11.x buster InRelease Get:7 http://packages.microsoft.com/repos/code stable/main arm64 Packages [16.0 kB] Get:8 http://packages.microsoft.com/repos/code stable/main armhf Packages [15.8 kB] Get:9 http://packages.microsoft.com/repos/code stable/main amd64 Packages [15.4 kB] Fetched 175 kB in 2s (72.7 kB/s) Reading package lists…
                        apt-get update completed ok
                        apt-get upgrade started
                        apt upgrade result =rc=0 Reading package lists…
                        Building dependency tree…
                        Reading state information…
                        Calculating upgrade…
                        The following packages have been kept back:
                        linux-headers-amd64:amd64 linux-image-amd64:amd64
                        0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
                        Installing helper tools …
                        Reading package lists…
                        Building dependency tree…
                        Reading state information…
                        build-essential is already the newest version (12.6).
                        curl is already the newest version (7.64.0-4+deb10u1).
                        git is already the newest version (1:2.20.1-2+deb10u3).
                        unzip is already the newest version (6.0-23+deb10u2).
                        wget is already the newest version (1.20.1-1.1).
                        wget set to manually installed.
                        0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
                        Check current Node installation …
                        Node currently installed. Checking version number.
                        Minimum Node version: v10.1.0
                        Installed Node version: v10.24.0
                        No Node.js upgrade necessary.
                        Check current NPM installation …
                        NPM currently installed. Checking version number.
                        Minimum npm version: V6.0.0
                        Installed npm version: V7.6.0
                        No npm upgrade necessary.
                        Cloning MagicMirror …
                        Cloning MagicMirror Done!
                        package.json update for x86 fontface completed ok
                        Installing dependencies …
                        Dependencies installation Done!
                        setting up initial config.js
                        Check plymouth installation …
                        Splashscreen: Checking themes directory.
                        Splashscreen: Create theme directory if not exists.
                        Splashscreen: Changed theme to MagicMirror successfully.
                        install and setup pm2
                        pm2 not installed, installing
                        pm2 install result npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) added 201 packages, and audited 202 packages in 19s 9 packages are looking for funding run npm fund for details found 0 vulnerabilities
                        get the pm2 platform specific startup command
                        startup command = sudo env PATH=$PATH:/usr/bin:/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi

                                            -------------
                        

                        /\\\\\\_/\\/\\/\\\\_
                        _/\/////////\_/\\\
                        /\\\/\///////\_
                        /\_
                        /\_/\//\_/\//\_/////\_
                        _/\\\\\\/
                        /\\///\/\/
                        /\_
                        /\/
                        /\/////////
                        /\_
                        ///\/
                        /\_/\//_____
                        /\_
                        /\_////\_____/\//_____
                        /\_/\_/\_/\/__________
                        /\_/\_/\_/\\\\\\\_
                        _////////////////////////

                                              Runtime Edition
                        
                            PM2 is a Production Process Manager for Node.js applications
                                         with a built-in Load Balancer.
                        
                                    Start and Daemonize any application:
                                    $ pm2 start app.js
                        
                                    Load Balance 4 instances of api.js:
                                    $ pm2 start api.js -i 4
                        
                                    Monitor in production:
                                    $ pm2 monitor
                        
                                    Make pm2 auto-boot at server restart:
                                    $ pm2 startup
                        
                                    To go further checkout:
                                    http://pm2.io/
                        
                        
                                            -------------
                        

                        [PM2] Init System found: systemd
                        Platform systemd
                        Template
                        [Unit]
                        Description=PM2 process manager
                        Documentation=https://pm2.keymetrics.io/
                        After=network.target

                        [Service]
                        Type=forking
                        User=pi
                        LimitNOFILE=infinity
                        LimitNPROC=infinity
                        LimitCORE=infinity
                        Environment=PATH=$PATH:/usr/bin:/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
                        Environment=PM2_HOME=/home/pi/.pm2
                        PIDFile=/home/pi/.pm2/pm2.pid
                        Restart=on-failure

                        ExecStart=/usr/local/lib/node_modules/pm2/bin/pm2 resurrect
                        ExecReload=/usr/local/lib/node_modules/pm2/bin/pm2 reload all
                        ExecStop=/usr/local/lib/node_modules/pm2/bin/pm2 kill

                        [Install]
                        WantedBy=multi-user.target

                        Target path
                        /etc/systemd/system/pm2-pi.service
                        Command list
                        [ ‘systemctl enable pm2-pi’ ]
                        [PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
                        [PM2] Making script booting at startup…

                        Executing: systemctl enable pm2-pi…

                        [PM2] [v] Command successfully executed.
                        ±--------------------------------------+
                        [PM2] Freeze a process list on reboot via:
                        $ pm2 save

                        [PM2] Remove init script via:
                        $ pm2 unstartup systemd
                        pm2 startup command done
                        configure the pm2 config file for MagicMirror
                        start MagicMirror via pm2 now
                        save MagicMirror pm2 config now
                        stop MagicMirror via pm2 now
                        disable screensaver via gsettings was true and uint32 300
                        disable screensaver via lightdm.conf
                        disable screensaver via lxsession
                        We’re ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.
                        install completed - Tue Mar 2 04:04:51 HST 2021

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 1 / 3
                        • 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