Skip to content
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? #5

Open
endquote opened this issue Dec 5, 2013 · 4 comments
Open

Module version mismatch? #5

endquote opened this issue Dec 5, 2013 · 4 comments

Comments

@endquote
Copy link

endquote commented Dec 5, 2013

I'm getting the following error when calling require('winston-winlog'):

module.js:356
  Module._extensions[extension](this, filename);
                               ^
Error: Module version mismatch. Expected 11, got 1.
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (..\node_modules\winston-winlog\node_modules\windows-eventlog\index.js:6:20)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

npm list shows:

winston-winlog@0.2.1 node_modules\winston-winlog
└── windows-eventlog@1.0.0

Winston is otherwise working fine with other transports enabled.

This is on Windows 8.1 x64.

@endquote
Copy link
Author

endquote commented Dec 5, 2013

If I install the windows-eventlog module on its own and require that, it works ok.

@jfromaniello
Copy link
Owner

I think this happens with every module when you npm install with one
version of node and then try to use with a different one.

@endquote
Copy link
Author

endquote commented Dec 5, 2013

My version of node hasn't changed, and this happens even if I wipe out all modules and reinstall them. Could it be a 32/64 bit issue?

On Dec 5, 2013, at 1:45 AM, José F. Romaniello notifications@github.com wrote:

I think this happens with every module when you npm install with one
version of node and then try to use with a different one.

Reply to this email directly or view it on GitHub.

@dynajoe
Copy link

dynajoe commented Mar 3, 2014

I have the same problem. I went from Node 0.8.20 to 0.10.26 and had this problem. I tried reinstalling the module but (windows-eventlog) was unable to build because I don't have VS 2010 anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants