[QUESTION] Clean pull of master won't load localhost:8080 on Windows OS
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:
- Administrator cmd shell
- npm i
- npm update
- npm run build-n (note that build-dev was tried too)
- npm start --> results in following: (I removed the full file paths)
grapesjs-master>npm run start
[email protected] start grapesjs-master npm run build:css -- -w & webpack-dev-server --open --progress --colors [email protected] build:css grapesjs-master node-sass src/styles/scss/main.scss dist/css/grapes.min.css --output-style compressed "-w"
I then fire up chrome and visit http://localhost:8080 and it says "localhost refused to connect."
I then tried specifying different port but that didn't work. Created a springboot sample app to verify that nothing was blocking port 8080 and that too was fine.
Ideas for me to try?
Thanks for any assistance you can provide much appreciated.
Answers (3)
switched over and pulled the preset web page repo .. now seeing what I expected.
Would also note that I ran tests and those executed and passed fine.
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/547/commits/2cc479ca2d4a6c43450d93d1738059c6792ef4f1)
Just tried running the latest grapesjs master on my home PC with same result: [Windows 8.1 x64, nodejs v6.4.0, npm v3.10.3]
$ npm start
[email protected] start C:\src\git\grapesjs npm run build:css -- -w & webpack-dev-server --open --progress --colors [email protected] build:css C:\src\git\grapesjs node-sass src/styles/scss/main.scss dist/css/grapes.min.css --output-style compressed "-w"
The above (just like my first report) is all that is shown and it just sits there, you have to terminate the job via ctrl-c.
npm install shows following warnings:
npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: [email protected] npm WARN optional Skipping failed optional dependency /webpack-dev-server/chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: [email protected]
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1249
[Question] Issue running on Cloud9
I'm trying to run this on Cloud9 but when I go to run it using the 'npm start' command it gives me the url of http://localhost:8080/ when I...
Issue #1179
[Question] Cannot load styles saved as !important
Hi! I'm trying to make all the user-set styles have the "!important" flag, in order to prevent some other previous existent classes to over...
Issue #930
[Question] Update resizer after asset changed
Hi! I trying to change default assets manager with ours custom manager. On double click the selected image is replaced with a new one with...
Issue #783
[QUESTION] Removing certain css
QUESTION My site consists of various webpages like home-page, category-page, results-page etc. The css for all the pages are in a single cs...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.