MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. kupperma
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    K
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 21
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Unable to install dependencies!

      @sdetweil Sorry, a bit late but it worked.

      The other issues are related to modules. I try first to solve it. I will come back if I get stuck.

      posted in Troubleshooting
      K
      kupperma
    • RE: Unable to install dependencies!

      @sdetweil what would I do without you ?

      I get this:

      npm run install:mm
      npm ERR! Missing script: "install:mm"
      npm ERR! 
      npm ERR! Did you mean one of these?
      npm ERR!     npm install # Install a package
      npm ERR!     npm run install-mm # run the "install-mm" package script
      npm ERR! 
      npm ERR! To see a list of scripts, run:
      npm ERR!   npm run
      
      npm ERR! A complete log of this run can be found in: /home/manfred/.npm/_logs/2024-02-10T18_21_24_984Z-debug-0.log
      
      

      I did the install-mm
      something is running

      posted in Troubleshooting
      K
      kupperma
    • Unable to install dependencies!
      Installing dependencies ...
      Unable to install dependencies! :eslint-plugin-jest: sill placeDep ROOT @typescript-eslint/utils@6.21.0 OK for: @stylistic/eslint-plugin-plus@1.6.1 want: ^6.20.0
      
      

      I checked following version:

      manfred@raspberrypi:~ $ node -v
      v20.8.0
      manfred@raspberrypi:~ $ npm -v
      10.4.0
      manfred@raspberrypi:~ $ eslint -v
      v6.4.0
      
      

      I also check via update-script:

      Check current Node installation ...
      Node currently installed. Checking version number.
      Minimum Node version: v20.8.0
      Installed Node version: v20.8.0
      No Node.js upgrade necessary.
      Check current NPM installation ...
      NPM currently installed. Checking version number.
      Minimum npm version: V10.1.0
      Installed npm version: V10.4.0
      No npm upgrade necessary.
      
      

      Why can’t the dependencies be installed?

      Manfred

      I tried it again, this time there is a wider explanation:

      <--- Last few GCs --->
      
      [34629:0x32d3dfa0]   163058 ms: Mark-Compact (reduce) 426.0 (440.9) -> 396.4 (405.4) MB, 44.66 / 0.04 ms  (+ 274.3 ms in 124 steps since start of marking, biggest step 29.7 ms, walltime since start of marking 887 ms) (average mu = 0.935, current mu = 0.75[34629:0x32d3dfa0]   168793 ms: Mark-Compact 472.5 (480.4) -> 472.1 (483.7) MB, 2788.15 / 0.00 ms  (average mu = 0.700, current mu = 0.513) allocation failure; scavenge might not succeed
      
      
      <--- JS stacktrace --->
      
      FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
       1: 0xc7b9cc node::Abort() [npm install]
       2: 0xb6e418 void node::FPrintF<>(_IO_FILE*, char const*) [npm install]
       3: 0xe79d2c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [npm install]
       4: 0xe79efc v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [npm install]
       5: 0x10818cc  [npm install]
       6: 0x1097da4 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [npm install]
       7: 0x1070b0c v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm install]
       8: 0x10718d0 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm install]
       9: 0x10508d0 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [npm install]
      10: 0x1042098 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [npm install]
      11: 0x10448bc v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [npm install]
      12: 0x119a4e0 v8::internal::JsonParser<unsigned short>::MakeString(v8::internal::JsonString const&, v8::internal::Handle<v8::internal::String>) [npm install]
      13: 0x119fbd4  [npm install]
      14: 0x11a1640 v8::internal::JsonParser<unsigned short>::ParseJson(v8::internal::Handle<v8::internal::Object>) [npm install]
      15: 0xf0c83c v8::internal::Builtin_JsonParse(int, unsigned long*, v8::internal::Isolate*) [npm install]
      16: 0x1862964  [npm install]
      Unable to install dependencies! 
      
      

      I do not understand the [npm install] !
      Does anyone understand this post of my RaspberryPi3B ?

      posted in Troubleshooting
      K
      kupperma
    • RE: googleAPIs for several modules

      @sdetweil Do I understand cerrectly?
      the two different credentials.json must work with the same OAuth Code?

      I just restarted the Mirror and now miraculously the Anniversaries are shown as well.
      I hope it stays like this.

      Thanks a lot Sam.

      posted in Troubleshooting
      K
      kupperma
    • googleAPIs for several modules

      Hi,
      i succesfully created an googleAPI for MMM-GoogleBirthdaysProvider it worked well until I created an googleAPI for MMM-GoogleTasks. Now GoogleTasks works but GoogleBirthdayProvider is no longer connected.

      What Do I have to do that both Modules work parallel?

      Thanks in advance for your responses.
      Manfred

      posted in Troubleshooting
      K
      kupperma
    • RE: New installation but even default is displayed

      @sdetweil

      Thank you again.
      MM2 is up and running.

      posted in Troubleshooting
      K
      kupperma
    • RE: New installation but even default is displayed

      I start over!
      Thanks for the checklist.
      I wont loose much for my custom.css , config.js I have the code copied in a textfile. The modules I would have to reinstall but thats ok.

      Thank you for your time.
      Manfred

      posted in Troubleshooting
      K
      kupperma
    • RE: New installation but even default is displayed

      I know what you mean:

      in an earlier installation I could move the mouse and the menubar got visible or I could press F11 and the menubar got visible. But now nothing works.
      So should I reinstall raspian and start from the beginning or is there a work a round?

      posted in Troubleshooting
      K
      kupperma
    • RE: New installation but even default is displayed

      The display does not react to ctrl-alt-t and there is no terminal visible.

      posted in Troubleshooting
      K
      kupperma
    • RE: New installation but even default is displayed

      Yes I have_
      Ok this does not work.
      So it seems to be raspianOS failure.

      posted in Troubleshooting
      K
      kupperma
    • 1 / 1