Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unsupported platform "windows"?

See original GitHub issue

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

Issue Analytics

State:
Created 5 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

9reactions

develarcommented, Jul 14, 2018

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

3reactions

mischniccommented, 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

Top Results From Across the Web

Unsupported platform: Windows 11 · Issue #719 · tj/n - GitHub

Installing from power shell windows 11 via npm returns unsupported PS C:\Users\vic85> npm install -g n npm ERR! code EBADPLATFORM npm ERR!

unsupported platform error trying to update intel drivers optane

Standard Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site ......

Running npm i on Windows results in EBADPLATFORM ...

I am getting Unsupported platform for fsevents@1.2.4 error while installing Angular. How to solve it? 94 · How to fix 'Unsupported platform for ......

Windows-AnyPC Unsupported Platform Type 0

I want to use the mobile emulator with Ionic2 Typescript cordova applications and deploy to windows 10 mobile devices. My first attempt to...

MSI Unsupported Platform - Error 1633 – Support - PDQ

Purpose: You want to resolve error 1633 - This installation package is not supported by this processor type. Resolution: The most...