Doesn't contain package.json file

[allancherianbiju]

Re: include npm module like firebase module into our own MM module

I’ve been trying for a while and I got the same error every single time.

WARNING! Could not load config file. Starting with default configuration. Error found: Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: electron-v3.0-linux-arm-glibc
Found: [node-v59-linux-arm-glibc]

cd ~/MagicMirror/modules/MMM-hellotsuhan
npm install --save-dev electron-rebuild
./node_modules/.bin/electron-rebuild

Tried executing this and I got this

How do I get that file?

:::

I’m very new to this.

:::

[sdetweil]

@allancherianbiju said in Doesn't contain package.json file:

Tried executing this and I got this

got what?

[allancherianbiju]

Formatting mistake. The error I posted isn’t showing up due to some reason.

npm ERR! Could not install from “node_modules/ .bin/electron-rebuild” as it does not contain a package.json file.

[sdetweil]

many components in a javascript application need to have their versions match the surrounding runtime. grpc is one of those… it will run in and outside the electron browser…

the electron-rebuild module is loaded as part of the base,
so you would do

cd ~/MagicMirror
node_modules/.bin/electron_rebuild

[allancherianbiju]

Just closing notes. I was able to fix this!

@sdetweil provided extra commands.

cd ~/MagicMirror
npm install electron-rebuild
node_modules/.bin/electron-rebuild

That worked for me, but I was faced with a new error.

Error: Cannot find module 'node_helper_.

Fixed that by running

cd -/MagicMirror
git checkout modules/node_modules/node_helper/index.js

Thanks for the help guys!

[allancherianbiju]

I had to reinstall MM and had to go through all of this again. Rebuilding electron fixed the issue and I found out that the git command I used doesn’t work anymore. Zzz… Updating should help.

cd -/MagicMirror
git checkout modules/node_modules/node_helper/index.js

[sdetweil]

@allancherianbiju in version 2.10 we fixed this problem, by moving the file to a different location.

[allancherianbiju]

@sdetweil Oh! That’s great! Onward, then :D