starred/log.io-NarrativeScience-old

Fork 0

mirror of https://github.com/NarrativeScience-old/log.io.git synced 2026-04-25 17:15:52 +03:00

[GH-ISSUE #102] Include Support for Windows #79

New issue

Closed

opened 2026-02-26 05:31:16 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 05:31:16 +03:00

Owner

Originally created by @szahn on GitHub (Nov 26, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/102

npm fails to install log.io on windows. Please provide support for Windows. I can provide the error logs from the install output if needed.

Originally created by @szahn on GitHub (Nov 26, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/102 npm fails to install log.io on windows. Please provide support for Windows. I can provide the error logs from the install output if needed.

kerem closed this issue

2026-02-26 05:31:16 +03:00

kerem commented

2026-02-26 05:31:17 +03:00

Author

Owner

@yobdcdoll commented on GitHub (Jan 26, 2014):

I failed to install log.io on windows 8. Error message shows as follows

C:\Users\lex\AppData\Roaming\npm\node_modules\log.io\node_modules\jquery\node_m odules\contextify\build\contextify.vcxproj(18,3): error MSB4019: The imported p roject "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. C:\Users\lex\AppData\Roaming\npm\node_modules\log.io\node_modules\socket.io-cli ent\node_modules\ws\build\bufferutil.vcxproj(18,3): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

@yobdcdoll commented on GitHub (Jan 26, 2014): I failed to install log.io on windows 8. Error message shows as follows C:\Users\lex\AppData\Roaming\npm\node_modules\log.io\node_modules\jquery\node_m odules\contextify\build\contextify.vcxproj(18,3): error MSB4019: The imported p roject "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. C:\Users\lex\AppData\Roaming\npm\node_modules\log.io\node_modules\socket.io-cli ent\node_modules\ws\build\bufferutil.vcxproj(18,3): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

kerem commented

2026-02-26 05:31:17 +03:00

Author

Owner

@bdmorin commented on GitHub (Oct 7, 2014):

I also tried in Cygwin and no dice. It's failing on contextify, but I'm not sure that's core issue.

@bdmorin commented on GitHub (Oct 7, 2014): I also tried in Cygwin and no dice. It's failing on contextify, but I'm not sure that's core issue.

kerem commented

2026-02-26 05:31:17 +03:00

Author

Owner

@kadaan commented on GitHub (Oct 17, 2014):

For me this solved the same problem with socket,io: npm install socket.io --msvs_version=2012

@kadaan commented on GitHub (Oct 17, 2014): For me this solved the same problem with socket,io: npm install socket.io --msvs_version=2012

kerem commented

2026-02-26 05:31:17 +03:00

Author

Owner

@ZaLiTHkA commented on GitHub (Jan 24, 2015):

This is not a log.io issue.. Pretty sure it comes down to your Windows environment configuration directly affecting the install-time requirements of socket.io. @kadaan shared half the solution in his post above.

Make sure you have either MS Visual Studio 2010 or 2012 installed (no need to run it, just have it's build tools on your %path%, which is handled by it's own installer), then install with the following command:

npm i -g log-io --msvs_version=2012

Naturally, if you have VS 2010 instead, use that for the version parameter.

For the record, I just installed this without any errors or warnings on my Win 8.1 x64 system. Tested with installing successfully through both Git's bash shell and Window's cmd. If you have build related issues, you can even try the same command in MSVS's own developer command lines (which is nothing more than cmd with additional environment variables loaded).

@ZaLiTHkA commented on GitHub (Jan 24, 2015): This is not a log.io issue.. Pretty sure it comes down to your Windows environment configuration directly affecting the install-time requirements of socket.io. @kadaan shared half the solution in his post above. Make sure you have either MS Visual Studio 2010 or 2012 installed (no need to run it, just have it's build tools on your `%path%`, which is handled by it's own installer), then install with the following command: ``` npm i -g log-io --msvs_version=2012 ``` Naturally, if you have VS 2010 instead, use that for the version parameter. For the record, I just installed this without any errors or warnings on my Win 8.1 x64 system. Tested with installing successfully through both Git's `bash` shell and Window's `cmd`. If you have build related issues, you can even try the same command in MSVS's own developer command lines (which is nothing more than `cmd` with additional environment variables loaded).

kerem commented

2026-02-26 05:31:17 +03:00

Author

Owner

@msmathers commented on GitHub (Jan 16, 2020):

v0.4x uses npm's built-in "bin" scripts for process invocation and no longer requires root/sudo access. It also uses the latest LTE version of node.js, and is likely to be a lot more compatible with most OSes.

@msmathers commented on GitHub (Jan 16, 2020): v0.4x uses npm's built-in "bin" scripts for process invocation and no longer requires root/sudo access. It also uses the latest LTE version of node.js, and is likely to be a lot more compatible with most OSes.

kerem referenced this issue

2026-02-26 05:31:43 +03:00

[PR #79] [CLOSED] Support in binaries for arguments with conf files #243