-
Notifications
You must be signed in to change notification settings - Fork 47
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
Error when I secondly run slater watch command #37
Comments
@kelfy thanks! I'll have a look at this. |
@kelfy what OS and Node version are you on? Also, would you mind trying something for me? Run
|
I can also confirm that I have the same issue when running two instances of slater in the same time. When I switch between themes, I need to shut one of them down to work on another one. Anyway, it's nothing serious. |
Thank you so much. Never thought about that. cheers for the comments. |
@kelfy hey no problem :) is your issue solved then? |
@estrattonbailey not entirely solved but managed to get around by force release port 4000. Is there a way to stop watching and release the port? |
@kelfy I'm sure there is. Would you mind having a look at my previous response and answering those questions? That would be super helpful. Thanks! |
@estrattonbailey I tried but nothing showing up. DIdn't notice it got live-reload. I am sure my theme is alright as I can browse online. |
This is first time I am using slater. When I first run "slater watch" which is fine. After I run "slater sync" then I come back and run "slater watch", the following error occur.
I've tried delete and whole theme and re-initialise the theme 3 times but no luck. Not sure what kind of error it is.
The text was updated successfully, but these errors were encountered: