Issue #830πŸ’¬ AnsweredOpened Feb 2, 2018by kewilson1 reactions

Clean pull of master won't load localhost:8080 on Windows OS

Quick answerby kewilson❀ 1

switched over and pulled the preset web page repo .. now seeing what I expected.

Read full answer below ↓

Question

Hi all, Having an issue after pulling latest master and simply trying to run, no modifications made at all. Environment: Windows 7, node 8.9.4_x64, npm 5.6.0, UAC = On Steps to reproduce: 1) Administrator cmd shell 2) npm i 3) npm update 4) npm run build-n (note that build-dev was tried too) 5) npm start --> results in following: (I removed the full file paths) grapesjs-master>npm run [email protected] start grapesjs-masternpm run build:css -- -w & webpack-dev-server --open --progress [email protected] build:css grapesjs-masternode-sass src/styles/scss/main.scss dist/css/grapes.min.c...

Answers (3)

kewilsonβ€’ Feb 3, 2018

switched over and pulled the preset web page repo .. now seeing what I expected.

kewilsonβ€’ Feb 2, 2018

Would also note that I ran tests and those executed and passed fine.

kewilsonβ€’ Feb 3, 2018

tl;dr - So does webpack-dev-server need to have cross-env in order to work on windows? I was able to run an older version of grapesjs that still used cross-env in its startup. It seems that the changes of this commit is the cause of the current difficulties: (https://github.com/artf/grapesjs/pull/5...

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.