Issues building Frontity on Windows

I’m opening this thread on behalf of paultitude a reddit user that has contacted me via private message there.

He is having trouble trying to build Frontity on his Windows machine, this is all the info he has provided:

@frontity/[email protected] build C:\Users\Paul\Desktop\frontity-mars-theme-example-1.1.13\packages\file-settings tsc --project ./tsconfig.build.json

<— Last few GCs —>

[7904:0000021DB6438E70] 24877 ms: Scavenge 1385.2 (1422.2) -> 1384.5 (1422.7) MB, 4.2 / 0.0 ms (average mu = 0.161, current mu = 0.125) allocation failure [7904:0000021DB6438E70] 24885 ms: Scavenge 1385.4 (1422.7) -> 1384.7 (1423.2) MB, 4.0 / 0.0 ms (average mu = 0.161, current mu = 0.125) allocation failure [7904:0000021DB6438E70] 24892 ms: Scavenge 1385.6 (1423.2) -> 1384.9 (1424.2) MB, 3.7 / 0.0 ms (average mu = 0.161, current mu = 0.125) allocation failure

<— JS stacktrace —>

==== JS stack trace =========================================

0: ExitFrame [pc: 0000033963DDC5C1]

Security context: 0x038a5c31e6e9 1: /* anonymous /(aka / anonymous */) [000002ED734E4041] [C:\Users\Paul\Desktop\frontity-mars-theme-example-1.1.13\node_modules\typescript\lib\tsc.js:~29] [pc=00000339645CC8A1](this=0x03369d7826f1 ,thisArg=0x03369d7826f1 ,body=0x03dc3d121921 <JSFunction (sfi = 00000031A0EDAF39)>) 2: getUnmatchedProperties(aka getUnmatchedPro…

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF71B63C6AA v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506 2: 00007FF71B617416 node::MakeCallback+4534 3: 00007FF71B617D90 node_module_register+2032 4: 00007FF71B93189E v8::internal::FatalProcessOutOfMemory+846 5: 00007FF71B9317CF v8::internal::FatalProcessOutOfMemory+639 6: 00007FF71BB17F94 v8::internal::Heap::MaxHeapGrowingFactor+9620 7: 00007FF71BB0EF76 v8::internal::ScavengeJob::operator=+24550 8: 00007FF71BB0D5CC v8::internal::ScavengeJob::operator=+17980 9: 00007FF71BB16317 v8::internal::Heap::MaxHeapGrowingFactor+2327 10: 00007FF71BB16396 v8::internal::Heap::MaxHeapGrowingFactor+2454 11: 00007FF71BC40637 v8::internal::factory::NewFillerObject+55 12: 00007FF71BCBD826 v8::internal::operator<<+73494 13: 0000033963DDC5C1 npm ERR! code ELIFECYCLE

Hey,

Thanks for posting this for me. I was trying to run the build and got the error above. Which environments has this been tested on?

Hey Paul!

Welcome to the community, thanks for joining in.

Can you please describe the steps you have followed to build Frontity on Windows? The framework should work correctly on that OS.

Hey Pablo,

Thank you :slight_smile: All I did was npm install which run well until the above error. Not really sure if this has been run on Windows before

Hi @paultitude, welcome to the forums :slight_smile:

Could you please run npx frontity info in the root folder of your project and paste the result here?

Hey @luisherranz,

Here you go :slight_smile:


## System:
 - OS: Windows 10
 - CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
 - Memory: 4.75 GB / 11.83 GB
## Binaries:
 - Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
 - npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
## Browsers:
 - Edge: 44.18362.329.0
 - Internet Explorer: 11.0.18362.1
## npmPackages:
 - @types/blob-util:  1.3.3 
 - @types/bluebird:  3.5.18 
 - @types/chai:  4.0.8 
 - @types/chai-jquery:  1.1.38 
 - @types/jquery:  3.3.6 
 - @types/lodash:  4.14.122 
 - @types/minimatch:  3.0.3 
 - @types/mocha:  5.2.7 
 - @types/sinon:  7.0.0 
 - @types/sinon-chai:  3.2.2 
 - cross-env: ^5.2.1 => 5.2.1 
 - cypress: ^3.4.1 => 3.4.1 
 - eslint: ^6.2.2 => 6.2.2 
 - eslint-plugin-cypress: ^2.6.1 => 2.6.1 
 - eslint-plugin-import: ^2.18.2 => 2.18.2 
 - eslint-plugin-jest: ^22.15.2 => 22.15.2 
 - eslint-plugin-jsx-a11y: ^6.2.3 => 6.2.3 
 - eslint-plugin-react: ^7.14.3 => 7.14.3 
 - husky: ^1.3.1 => 1.3.1 
 - lerna: ^3.15.0 => 3.15.0 
 - lint-staged: ^8.1.4 => 8.1.4 
 - memo-parser:  0.2.0 
 - prettier: ^1.16.4 => 1.16.4 
 - typescript: ^3.4.5 => 3.4.5 
## npmGlobalPackages:
 - frontity: Not Found
 - npx: Not Found

Ooooh, I was trying to run those from Github, never mind, all good now :slight_smile:

2 Likes