github-starred/proton-native
2
0
Fork 0
mirror of https://github.com/kusti8/proton-native.git synced 2026-05-15 14:15:50 -06:00
Code Issues 88 Projects Packages Wiki Activity Actions

[GH-ISSUE #166] Unsupported platform "windows"? #108

New issue
Closed
opened 2026-05-05 11:43:03 -06:00 by gitea-mirror · 11 comments
gitea-mirror commented 2026-05-05 11:43:03 -06:00
Owner
Copy link

Originally created by @Bizarrus on GitHub (Jul 13, 2018).
Original GitHub issue: https://github.com/kusti8/proton-native/issues/166

info@DESKTOP-B1MR61C MINGW64 ~/Documents/GitHub/RIDE
$ npm run dist

> RIDE@0.0.1 dist C:\Users\info\Documents\GitHub\RIDE
> electron-builder

  • electron-builder version=20.20.4
  • loaded configuration file=package.json ("build" field)
  • description is missed in the package.json appPackageFile=C:\Users\info\Documents\GitHub\RIDE\package.json
  • author is missed in the package.json appPackageFile=C:\Users\info\Documents\GitHub\RIDE\package.json
  • packaging       platform=win32 arch=x64 proton=10.6.0 appOutDir=dist\win-unpacked
Error: Unsupported platform: windows
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\ProtonFramework.ts:115:10
    at Generator.next (<anonymous>)
    at deleteItem (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\empty\index.js:20:25)
    at fs.readdir (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\empty\index.js:16:5)
    at FSReqWrap.oncomplete (fs.js:145:20)
From previous event:
    at ProtonFramework.prepareApplicationStageDirectory (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\ProtonFramework.ts:117:6)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:172:21
    at Generator.next (<anonymous>)
From previous event:
    at WinPackager.doPack (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:157:165)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:112:16
    at Generator.next (<anonymous>)
From previous event:
    at WinPackager.pack (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:110:95)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:369:24
    at Generator.next (<anonymous>)
    at xfs.stat (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\mkdirs\mkdirs.js:56:16)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\graceful-fs\polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:159:5)
From previous event:
    at Packager.doBuild (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:337:39)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:313:52
From previous event:
    at Packager._build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:290:133)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:286:23
    at Generator.next (<anonymous>)
    at runCallback (timers.js:696:18)
    at tryOnImmediate (timers.js:667:5)
    at processImmediate (timers.js:649:5)
From previous event:
    at Packager.build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:243:14)
    at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\index.ts:52:40
    at Generator.next (<anonymous>)
From previous event:
    at build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\out\index.js:220:17)
    at build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder\src\builder.ts:224:10)
    at then (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder\src\cli\cli.ts:42:48)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! RIDE@0.0.1 dist: `electron-builder`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the RIDE@0.0.1 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\info\AppData\Roaming\npm-cache\_logs\2018-07-13T23_07_03_783Z-debug.log
Originally created by @Bizarrus on GitHub (Jul 13, 2018). Original GitHub issue: https://github.com/kusti8/proton-native/issues/166 ``` info@DESKTOP-B1MR61C MINGW64 ~/Documents/GitHub/RIDE $ npm run dist > RIDE@0.0.1 dist C:\Users\info\Documents\GitHub\RIDE > electron-builder • electron-builder version=20.20.4 • loaded configuration file=package.json ("build" field) • description is missed in the package.json appPackageFile=C:\Users\info\Documents\GitHub\RIDE\package.json • author is missed in the package.json appPackageFile=C:\Users\info\Documents\GitHub\RIDE\package.json • packaging platform=win32 arch=x64 proton=10.6.0 appOutDir=dist\win-unpacked Error: Unsupported platform: windows at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\ProtonFramework.ts:115:10 at Generator.next (<anonymous>) at deleteItem (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\empty\index.js:20:25) at fs.readdir (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\empty\index.js:16:5) at FSReqWrap.oncomplete (fs.js:145:20) From previous event: at ProtonFramework.prepareApplicationStageDirectory (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\ProtonFramework.ts:117:6) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:172:21 at Generator.next (<anonymous>) From previous event: at WinPackager.doPack (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:157:165) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:112:16 at Generator.next (<anonymous>) From previous event: at WinPackager.pack (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\platformPackager.ts:110:95) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:369:24 at Generator.next (<anonymous>) at xfs.stat (C:\Users\info\Documents\GitHub\RIDE\node_modules\fs-extra\lib\mkdirs\mkdirs.js:56:16) at C:\Users\info\Documents\GitHub\RIDE\node_modules\graceful-fs\polyfills.js:287:18 at FSReqWrap.oncomplete (fs.js:159:5) From previous event: at Packager.doBuild (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:337:39) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:313:52 From previous event: at Packager._build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:290:133) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:286:23 at Generator.next (<anonymous>) at runCallback (timers.js:696:18) at tryOnImmediate (timers.js:667:5) at processImmediate (timers.js:649:5) From previous event: at Packager.build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\packager.ts:243:14) at C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\src\index.ts:52:40 at Generator.next (<anonymous>) From previous event: at build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder-lib\out\index.js:220:17) at build (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder\src\builder.ts:224:10) at then (C:\Users\info\Documents\GitHub\RIDE\node_modules\electron-builder\src\cli\cli.ts:42:48) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! RIDE@0.0.1 dist: `electron-builder` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the RIDE@0.0.1 dist script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\info\AppData\Roaming\npm-cache\_logs\2018-07-13T23_07_03_783Z-debug.log ```
gitea-mirror commented 2026-05-05 11:43:12 -06:00
Author
Owner
Copy link

@maciek134 commented on GitHub (Jul 14, 2018):

Shouldn't platform be win32 or win64 instead of windows?

<!-- gh-comment-id:405005513 --> @maciek134 commented on GitHub (Jul 14, 2018): Shouldn't platform be `win32` or `win64` instead of `windows`?
gitea-mirror commented 2026-05-05 11:43:16 -06:00
Author
Owner
Copy link

@mischnic commented on GitHub (Jul 14, 2018):

No, electron-packager electron-builder doesn't support Windows for proton-native (yet - @develar ?)

<!-- gh-comment-id:405006416 --> @mischnic commented on GitHub (Jul 14, 2018): No, ~electron-packager~ [electron-builder](https://github.com/electron-userland/electron-builder) doesn't support Windows for proton-native (yet - @develar ?)
gitea-mirror commented 2026-05-05 11:43:20 -06:00
Author
Owner
Copy link

@develar commented on GitHub (Jul 14, 2018):

Ok, I guess it is a first user report and I need definitely finish support Windows.

<!-- gh-comment-id:405006643 --> @develar commented on GitHub (Jul 14, 2018): Ok, I guess it is a first user report and I need definitely finish support Windows.
gitea-mirror commented 2026-05-05 11:43:22 -06:00
Author
Owner
Copy link

@nicostuhlfauth commented on GitHub (Aug 2, 2018):

Same problem here. @develar Is there any workaround? Otherwise, how long will it take to get it running?

<!-- gh-comment-id:409880332 --> @nicostuhlfauth commented on GitHub (Aug 2, 2018): Same problem here. @develar Is there any workaround? Otherwise, how long will it take to get it running?
gitea-mirror commented 2026-05-05 11:43:24 -06:00
Author
Owner
Copy link

@mischnic commented on GitHub (Aug 2, 2018):

@nicostuhlfauth You could try using launchui-packager.
I've set up an example repo for proton-native: https://github.com/mischnic/proton-launchui

<!-- gh-comment-id:409987096 --> @mischnic commented on GitHub (Aug 2, 2018): @nicostuhlfauth You could try using [launchui-packager](https://github.com/mimecorg/launchui-packager). I've set up an example repo for proton-native: https://github.com/mischnic/proton-launchui
gitea-mirror commented 2026-05-05 11:43:26 -06:00
Author
Owner
Copy link

@nicostuhlfauth commented on GitHub (Aug 3, 2018):

@mischnic Doesn't work for me with create-proton-app. Even the blank project throws a "Module did not self-register" error. Any idea?

<!-- gh-comment-id:410159245 --> @nicostuhlfauth commented on GitHub (Aug 3, 2018): @mischnic Doesn't work for me with `create-proton-app`. Even the blank project throws a "Module did not self-register" error. Any idea?
gitea-mirror commented 2026-05-05 11:43:29 -06:00
Author
Owner
Copy link

@mischnic commented on GitHub (Aug 3, 2018):

Doesn't work for me with create-proton-app. Even the blank project throws a "Module did not self-register" error.

What do you mean by that? Please try cloning proton-launchui, copying your source files into the src folder and running npm run package.

<!-- gh-comment-id:410170433 --> @mischnic commented on GitHub (Aug 3, 2018): > Doesn't work for me with create-proton-app. Even the blank project throws a "Module did not self-register" error. What do you mean by that? Please try cloning proton-launchui, copying your source files into the src folder and running `npm run package`.
gitea-mirror commented 2026-05-05 11:43:31 -06:00
Author
Owner
Copy link

@nicostuhlfauth commented on GitHub (Aug 3, 2018):

Ah ok I got it running. Switched from the default build script that create-proton-app created to webpack with babel-loader. Thanks @mischnic 😄

<!-- gh-comment-id:410177878 --> @nicostuhlfauth commented on GitHub (Aug 3, 2018): Ah ok I got it running. Switched from the default build script that `create-proton-app` created to webpack with babel-loader. Thanks @mischnic 😄
gitea-mirror commented 2026-05-05 11:43:33 -06:00
Author
Owner
Copy link

@ateshuseyin commented on GitHub (Sep 28, 2018):

windows 10
node: v8.12.0
npm: 6.4.1

the same problem :(

<!-- gh-comment-id:425430485 --> @ateshuseyin commented on GitHub (Sep 28, 2018): windows 10 node: v8.12.0 npm: 6.4.1 the same problem :(
gitea-mirror commented 2026-05-05 11:43:35 -06:00
Author
Owner
Copy link

@icyJoseph commented on GitHub (Oct 13, 2018):

I guess the windows support is not out yet? I am also getting the
Error: Unsupported platform: windows,
error, when running yarn dist.

<!-- gh-comment-id:429515148 --> @icyJoseph commented on GitHub (Oct 13, 2018): I guess the windows support is not out yet? I am also getting the `Error: Unsupported platform: windows`, error, when running `yarn dist`.
gitea-mirror commented 2026-05-05 11:43:36 -06:00
Author
Owner
Copy link

@mischnic commented on GitHub (Dec 9, 2018):

Windows is now supported by electron-builder!

<!-- gh-comment-id:445572271 --> @mischnic commented on GitHub (Dec 9, 2018): Windows is now supported by electron-builder!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/npm_and_yarn/examples/CatApi/json5-1.0.2
dependabot/npm_and_yarn/examples/Calculator/json5-1.0.2
dependabot/npm_and_yarn/examples/CatApi/json5-and-webpack-and-webpack-cli-and-babel-loader-2.2.3
dependabot/npm_and_yarn/examples/Calculator/qs-6.5.3
dependabot/npm_and_yarn/examples/CatApi/decode-uri-component-0.2.2
dependabot/npm_and_yarn/examples/Calculator/decode-uri-component-0.2.2
dependabot/npm_and_yarn/examples/Notepad/decode-uri-component-0.2.2
dependabot/npm_and_yarn/examples/Calculator/loader-utils-1.4.2
dependabot/npm_and_yarn/examples/CatApi/loader-utils-and-webpack-cli-1.4.2
dependabot/npm_and_yarn/examples/Calculator/terser-4.8.1
dependabot/npm_and_yarn/examples/CatApi/terser-4.8.1
dependabot/npm_and_yarn/examples/CatApi/node-fetch-2.6.7
dependabot/npm_and_yarn/examples/Calculator/shell-quote-1.7.3
dependabot/npm_and_yarn/examples/CatApi/shell-quote-1.7.3
dependabot/npm_and_yarn/examples/Notepad/shell-quote-1.7.3
dependabot/npm_and_yarn/examples/Calculator/ajv-6.12.6
dependabot/npm_and_yarn/examples/Calculator/tar-4.4.19
dependabot/npm_and_yarn/examples/Notepad/tar-4.4.19
dependabot/npm_and_yarn/examples/CatApi/tar-4.4.19
dependabot/npm_and_yarn/examples/Calculator/path-parse-1.0.7
dependabot/npm_and_yarn/examples/CatApi/path-parse-1.0.7
dependabot/npm_and_yarn/examples/Notepad/path-parse-1.0.7
dependabot/npm_and_yarn/examples/Notepad/ws-7.4.6
dependabot/npm_and_yarn/examples/CatApi/ws-7.4.6
dependabot/npm_and_yarn/examples/Calculator/ws-7.4.6
dependabot/npm_and_yarn/examples/Calculator/browserslist-4.16.6
dependabot/npm_and_yarn/examples/Calculator/hosted-git-info-2.8.9
dependabot/npm_and_yarn/examples/Calculator/lodash-4.17.21
dependabot/npm_and_yarn/examples/Notepad/lodash-4.17.21
dependabot/npm_and_yarn/examples/Calculator/ua-parser-js-0.7.28
dependabot/npm_and_yarn/examples/Notepad/ua-parser-js-0.7.28
dependabot/npm_and_yarn/examples/CatApi/lodash-4.17.21
dependabot/npm_and_yarn/examples/CatApi/ua-parser-js-0.7.28
dependabot/npm_and_yarn/examples/CatApi/ssri-6.0.2
dependabot/npm_and_yarn/examples/Calculator/ssri-6.0.2
dependabot/npm_and_yarn/examples/Calculator/y18n-4.0.1
dependabot/npm_and_yarn/examples/CatApi/y18n-4.0.1
dependabot/npm_and_yarn/examples/CatApi/elliptic-6.5.4
dependabot/npm_and_yarn/examples/Calculator/elliptic-6.5.4
dependabot/npm_and_yarn/examples/Calculator/ini-1.3.8
dependabot/npm_and_yarn/examples/Notepad/ini-1.3.8
dependabot/npm_and_yarn/examples/CatApi/ini-1.3.7
dependabot/npm_and_yarn/examples/CatApi/yargs-parser-13.1.2
dependabot/npm_and_yarn/examples/Calculator/yargs-parser-13.1.2
dependabot/npm_and_yarn/examples/CatApi/acorn-6.4.1
dependabot/npm_and_yarn/examples/Calculator/acorn-6.4.1
dependabot/npm_and_yarn/acorn-5.7.4
v2
issue-templates
tests
yoga
No results found.
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
libui issue

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
wait for libui implementation
No labels
bug
documentation
enhancement
libui issue
pull-request
question
wait for libui implementation
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/proton-native#108
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?