$ npm run build - in Windows

[max-mapper]

$ npm run build - in Windows

[carletto]

I have Solved!
I renamed the file electron.js in main.js and i 've modified the parameters inside package.json

After cancel electron.js from directory.

package.json:
{
"name": "screencat",
"version": "4.2.0",
"description": "webrtc screensharing with shared mouse and keyboard",
"main": "main.js",
"scripts": {
"start": "electron main.js",
....

Now screencat starts! But I have others errors on deprecated function and on robot.js but this is another story ;-)

[max-mapper]

hi @skyview059, windows support is experimental but it was built last week successfully on windows by someone else. there are windows specific instructions here: https://github.com/maxogden/screencat#building-the-app

[eduardofg]

hi @maxogden, I tryed build in windows, but when executed (npm start), I get an error (in line 1 and char 1). Do you have any idea? Tks a lot

[mafintosh]

@eduardofg what's the error?

[eduardofg]

hi, @mafintosh, It's an error 800A138F, in electron.js, the same if you execute the .js manually.

[eduardofg]

Hi @mafintosh and @maxogden, I didn't had installed the electron runtime (sorry)(http://maxogden.com/electron-fundamentals.html). I started the electron.js but I not understand what the next step. I need start the app.js with node too? Thanks a lot

[carletto]

I have the same error 800A138F in win 7 on npm start... How I fix? Thaks

[eduardofg]

hi @carletto. Install the prebuilt of electron (npm install electron-prebuilt -g), now the comand "electron" works. (electron electron.js), but out of directory "screencat". If you execute "electron" its open a new window, for you put the application. I dragged and drop the electron.js and its execute (ready on console). But now, I not understand the next step for execute....

[fritx]

yeah, same here..
in windows, electron electron.js would just open up the file electron.js
need to either rename the electron.js or c:\path\to\electron electron.js

[mattwkelly]

Thanks for posting the fixes. Confirming these work, but now when I run 'npm start' it's stuck-- it just says 'ready' in console.

Edit: In my tiredness, I didn't notice screencat is actually running. :) So this issue is resolved for me.

[zhanls]

Thanks for posting the fixes again. It works in my pc at least.
Though you just have to find the "hidden" the black cat in the windows 10 task bar: