name conflict - electron(atom-shell)

[romgrk]

Hello,

I would just like to highlight the fact that this package has a name conflict with https://github.com/atom/electron, and that it might be a good thing to advertise the fact that a name-conflict exists. (executable file is called electron in both packages)

Thanks

[dmr]

This naming problem is causing a lot of conflicts: https://github.com/atom/electron/issues/3708

[romgrk]

@logicalparadox up. This can make you loose quite a lot of time. I won't make the mistake again, but think that every developer that makes the mistake of running npm install electron instead of npm install electron-prebuilt will loose time. Please advertise the fact that a name-conflict exists.

[jacobq]

+1; I know it's not your fault that they picked the same name as you were using (looks like your first commit here was in 2012 and the atom shell -> electron rename happened in 2015, I believe), but because their project is far more well-known it can be quite confusing to mistakenly run npm install --save electron (to install atom/electron), have it succeed, but then get unexpected errors further down the line.

[Hypercubed]

I had the same issue. Installing logicalparadox/matcha (which depends on electron) broke juliangruber/browser-run (which uses electron-prebuilt). To fix this with npm v3.9 I did the following:

npm install matcha
npm uninstall electron
cd node_modules/matcha
npm install

[chocolateboy]

It's even more confusing now that GitHub's project is called electron on npm (and has been since 2016-07-28).