Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fractal start --sync does not load local server #160

Closed
DadaConsultant opened this issue Oct 6, 2016 · 20 comments
Closed

fractal start --sync does not load local server #160

DadaConsultant opened this issue Oct 6, 2016 · 20 comments

Comments

@DadaConsultant
Copy link

On windows environment - when you set up fractal using the guide provided on the site. Running fractal start --sync only try to open fractal.js but fails to launch the web server UI.

@DadaConsultant
Copy link
Author

DadaConsultant commented Oct 6, 2016

nevermind, resolved the issue. I wasn't running the command from the 'public/' folder created in my root dir

@allmarkedup
Copy link
Member

@DadaConsultant Glad you got it working - however it shouldn't actually need to be run from the public directory, it should work from the project root directory, so that may be a bug - I'll look into it.

@schnubb
Copy link

schnubb commented Jan 20, 2017

It mustn't be the public directory, but on cmd you have to start fractal from a subdirectory.
Anything new on this bug?

@siiron
Copy link

siiron commented Feb 15, 2017

Having the same issue on Windows 10 running node v6.9.5 and fractal v1.1.3. Any progress investigating fixing this?

@mja202
Copy link

mja202 commented Apr 10, 2017

Having the same problem on Mac. Work around for me is to start the Fractal CLI and then start the server from there.

Using yarn:
yarn run fractal

Within fractal:
start --sync

@serslon
Copy link

serslon commented Apr 11, 2017

I fixed this problem after run command
npm install vorpal@1.11.4

But I have fractal version 1.0.8

@dkhuntrods
Copy link
Member

@mja202 @serslon There was an issue with an updated version of vorpal, see this thread for more details: #232

@trickydisco78
Copy link

I#'m having the same issue on windows.

Jsut tried the same as mj202 recommended and it worked!

@julkue
Copy link

julkue commented Jun 15, 2017

Just went into this issue too. Fractal seems to be a great idea, but it needs more love. The approach of @mja202 isn't a solution, just a workaround.

@julkue
Copy link

julkue commented Jun 15, 2017

Btw: What you can do to speed it up in one command is: yarn run fractal -- start --sync

@mja202
Copy link

mja202 commented Jun 15, 2017

Yes, it was a workaround. However, the current fractal (@1.1.4) works as it should (at least for me).

When fractal is installed globally (yarn global add @frctl/fractal) then fractal start sync within a project should just work.

@allmarkedup
Copy link
Member

@julmot @trickydisco78 can you confirm that you are using the latest release (1.1.4)? This was caused by a breaking change in the version of Vorpal that was used but it was bumped in the latest release and should work now.

@julkue
Copy link

julkue commented Jun 16, 2017

@allmarkedup I was using 1.1.4, yes.

@julkue
Copy link

julkue commented Jun 19, 2017

I was able to get it to work with this workaround.

@ten1seven
Copy link

ten1seven commented Sep 18, 2017

After using Fractal on a project for about 9 months, I'm suddenly experiencing this, using version 1.1.5.

I've verified this issue by installing a brand new blank Fractal site on my machine and on a colleague's machine that's never run Fractal before. As the below screenshot shows, after running fractal start --sync, Fractal starts, shows a localhost address, then the process seems to quit silently.

s4jbxh

@julkue
Copy link

julkue commented Sep 18, 2017

I'm experiencing the same. Here's something strange going on, probably due to #346.

@meerestier
Copy link

Same here

@dkhuntrods
Copy link
Member

@ten1seven @meerestier
An unsupervised Greenkeeper update broke 1.1.6 - I've just pushed v1.1.7 that rolls back that update, so if it was due to that, this version should fix it.

@davidDuymelinck
Copy link

The update fixes the problem for me on macos

@stale
Copy link

stale bot commented Jul 12, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 12, 2018
@stale stale bot closed this as completed Jul 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests