Using npm > 3 will cause packaging to miss dependencies about electron-react-boilerplate

[rbkreisberg]

It looks like the same thing can happen with npm 2. When the devDependency version of async is close enough to the child dep of a production dependency, that linked dep is lost.

[jhen0409]

In my work project, I using a new folder to build (including package.json), and run npm i --production reinstall dependencies, it seems to solved this problem, @chentsulin you think? Or do we use webpack in main script? :D

[chentsulin]

Maybe we can give electron-packager's opts prune a try and see whether it works on npm@3 or not.

[rbkreisberg]

@jhen0409 How do you run the build without the devDependencies present in the project? Does this mean that electron-packager and the other build tools are being pulled into the compiled app?

[rbkreisberg]

I tried the following:

added npm as a devDependency
npm install npm --save-dev

Identify production only (or dev only) dependencies using the following

npm.load({json:true, parseable: true, production: true}, function(err) {
      npm.ls([], function(err, data, lite) {
         console.log(data);
          console.log(lite);
       });
});

but either this is broken or the parameters are wrong.

[jhen0409]

@rbkreisberg no, I just create new a child folder (copy package.json to it, use --production to install or copy node_modules then prune), so build is work on parent folder, but it only packaging for node_modules of the child folder.

[jhen0409]

@chentsulin electron-packager's prune it works! @rbkreisberg you can try in this.

[rbkreisberg]

@jhen0409 @chentsulin thanks. I used prune for a while and took it out after rebasing to a more recent version of electron-react-boilerplate. Adding it back in solved my issue!