-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module version mismatch. Expected 48, got 47. #453
Comments
|
Please update to node 6.2.0. and |
@develar Thanks for your help. That seems to have done the trick, but I have to confess that I'm not sure why. I can't think of anything that should've changed (locally) since I last ran things. Would you mind taking a minute to explain what you clearly knew would change so I'll be more educated the next time around? |
Well, |
@develar 😀 Fair enough. Thanks again. |
After spending a day on this I figured out the answer. If all else fails you need to install your packages and then run npm rebuild --runtime=electron --target=1.3.4 --disturl=https://atom.io/download/atom-shell --abi=49 where 1.3.4 is your electron version and 49 is the abi it's expecting. |
@TomAshley303 Please see #683 |
@TomAshley303 work for me, |
The only solution working for me was with this command: Once added, my app works with "npm start" and after packing. Also notice that I'm using windows. See ya! |
Thanks a lot @develar |
(Windows users) You can manage your node version with node version manager: |
I'm working on a project that often runs hot and cold. As it happens, I haven't run a build in a little over a month (it's been a cold period). At the time, it worked just fine. Today, though, I tried to run a build and got this:
In my project root, I have the following package.json:
I run the build by simply executing
Locally, I'm running Node v6.0.0.
My issue seems similar to #39, but I'm not certain of that. I've been looking around for a map of electron version to the packaged node version, but haven't found one yet. Any advice would be a big help.
The text was updated successfully, but these errors were encountered: