Unable to run on windows

Hi Guys, I am having a problem on windows.

caret keeps blinking after i type npx frontity dev , No logs, No Errors just the blinking caret.

Could you please do a npx frontity info in your project folder and paste it here?

Also, could you please upload a screenshot of the console when it gets stuck?

System:

  • OS: Windows 10
  • CPU: (8) x64 Intel® Coreâ„¢ i7-6700HQ CPU @ 2.60GHz
  • Memory: 8.74 GB / 15.90 GB

Binaries:

  • Node: 10.15.3 - C:\Program Files\nodejs\node.EXE
  • npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

Browsers:

  • Edge: 44.17763.1.0
  • Internet Explorer: 11.0.17763.592

npmPackages:

  • @frontity/core: ^1.2.0 => 1.2.0
  • @frontity/html2react: ^1.1.8 => 1.1.8
  • @frontity/mars-theme: file:packages/mars-theme => 1.1.8
  • @frontity/tiny-router: ^1.0.13 => 1.0.13
  • @frontity/wp-source: ^1.2.0 => 1.2.0
  • @material-ui/core: ^4.4.1 => 4.4.1
  • @material-ui/icons: ^4.4.1 => 4.4.1
  • @material-ui/lab: ^4.0.0-alpha.26 => 4.0.0-alpha.26
  • axios: ^0.19.0 => 0.19.0
  • frontity: ^1.3.0 => 1.3.0
  • moment: ^2.24.0 => 2.24.0
  • react-credit-cards: ^0.7.0 => 0.7.0
  • react-moment: ^0.9.2 => 0.9.2
  • react-script-loader-hoc: ^1.2.2 => 1.2.2
  • react-stripe-checkout: ^2.6.3 => 2.6.3
  • react-stripe-elements: ^5.0.0 => 5.0.0
  • react-twitter-embed: ^2.0.8 => 2.0.8
  • recompose: ^0.30.0 => 0.30.0
  • sweetalert2-react: ^0.8.3 => 0.8.3

npmGlobalPackages:

  • frontity: Not Found
  • npx: Not Found

Was this problem working before? Did you add an image to the project?

Its working on my Mac OS. I pushed the code to github and cloned project on a different Windows OS and having this issue.

I tried to create a new project and it works all fine on windows.

P.S i cloned the same repo on Ubuntu and it was was having the same problem but installing frontity/core fixed the problem

Did you add an image to the project? We’ve just fixed a bug in Windows with images: https://github.com/frontity/frontity/issues/189

@luisherranz yes, my project has a few images

We’ve just released a fix for that in @frontity/core v1.2.1. Could you please do npm update in your project and let me know if it is fixed?