-
Notifications
You must be signed in to change notification settings - Fork 255
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
Installation on Windows 10 still fails because of missing headers #249
Comments
I do not use windows. But the bare What version of npm are you using? |
6.4.1. Other commenters elsewhere have had success with installing via |
Hello @rreed, did you find a solution about this problem ? I unzipped the WinPcap 4.1.2 Developer's Pack in my C:\ directory & added to my environment variable but still not working. I'm out of idea ... |
Me neither, trying to find a solution! |
Yes, I used cap instead, since no one ever really responded here. :p It's good enough for my usecases, and might also be for yours, but obviously YMMV. |
This module has never supported (and can't easily support) windows.
You can work around this by doing blocking reads in an additional thread, which is what |
Hi, I fork the repo, and mirgrate to windows platform with npcap, change point:
welcome review https://github.com/frankie-zeng/node_npcap |
hi, awesome! feel free to open a PR with your changes. (I don't have much time now, though... sorry) some notes if you want to open a PR:
|
The last comment on #196 is "what about windows?", but there hasn't really been any motion there for a while, even though this seems to have been fixed on OSX and the various Linuces.
A bare
npm install
does not work, which is relatively known by this point:Others have worked around this on non-Windows OSes by installing via https instead, but that also does not work, because it searches for
pcap.h
in the recently creatednode_modules
subfolder and that doesn't exist:I have installed WinPcap, as well as Npcap, its non-deprecated friend which "works on Windows 10"; neither actually makes node not choke here.
Thoughts?
The text was updated successfully, but these errors were encountered: