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

[Bug] Beta 1: Problems with watcher (SCSS & PHP) #1804

Closed
5 of 6 tasks
emilsgulbis opened this issue Jan 11, 2017 · 6 comments · Fixed by #1806
Closed
5 of 6 tasks

[Bug] Beta 1: Problems with watcher (SCSS & PHP) #1804

emilsgulbis opened this issue Jan 11, 2017 · 6 comments · Fixed by #1806
Labels

Comments

@emilsgulbis
Copy link

Submit a feature request or bug report

Bug report

Steps

  1. composer create-project roots/sage my-theme dev-master
  2. npm install
  3. edited config.json
  4. yarn run start

Opens localhost:3000 but with console errors:
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:3000/app/themes/my-theme/dist/a8794502c051d1cd8213.hot-update.json
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:3000/app/themes/my-theme/dist/styles/main.css

Also terminal prints - https://discourse.roots.io/t/sage9-not-inserting-styles-in-browsersync/8525/7?u=emilsgulbis
No PHP files edited, but watcher called.

Please describe your local environment:

WordPress version: 4.7

OS: macOS Sierra

NPM/Node version: 4.0.5 / 7.4.0

Where did the bug happen? Development or remote servers?

Development

Is there a related Discourse thread or were any utilized (please link them)?

https://discourse.roots.io/t/sage9-not-inserting-styles-in-browsersync/8525/7

@emilsgulbis emilsgulbis changed the title Problems with watcher (SCSS & PHP) [Bug] Problems with watcher (SCSS & PHP) Jan 11, 2017
@retlehs retlehs added the bug label Jan 11, 2017
@retlehs retlehs mentioned this issue Jan 11, 2017
@emilsgulbis
Copy link
Author

emilsgulbis commented Jan 12, 2017

Not working for me.
Just created new sage theme and run yarn run start and no css was loaded (404 error on browser console) and same after styling update & browsersync refresh.

yarn run build works as expected and have no 404 errors on css files.

https://youtu.be/zTC6R0sa7f0

@giacomoalonzi
Copy link

after alpha1, I always had this problem.

@retlehs
Copy link
Sponsor Member

retlehs commented Jan 12, 2017

a copy of my reply to @emilsgulbis from discourse:

@emilsgulbis I noticed that when you open your console at the start of the BS session that you're missing the error I mention at the top of #1806

Uncaught TypeError: __WEBPACK_IMPORTED_MODULE_2__util_Router__[false] is not a constructor
    at Object.<anonymous> (main.js:23)
    at Object.<anonymous> (main.js:27)
    at __webpack_require__ (bootstrap f2d9dd8…:659)
    at fn (bootstrap f2d9dd8…:83)
    at Object.<anonymous> (tether.js:1811)
    at __webpack_require__ (bootstrap f2d9dd8…:659)
    at bootstrap f2d9dd8…:708
    at bootstrap f2d9dd8…:708

Can you remove your node_modules folder, make sure yarn.lock is the same as what's on the Sage repo, and re-run yarn?

@giacomoalonzi did you try making this change and then following the instructions at the top of #1806?

please keep the support back-and-forth on the discourse thread for this specific issue:

https://discourse.roots.io/t/sage9-not-inserting-styles-in-browsersync/8525

@retlehs retlehs changed the title [Bug] Problems with watcher (SCSS & PHP) [Bug] Beta 1: Problems with watcher (SCSS & PHP) Jan 12, 2017
@giacomoalonzi
Copy link

@retlehs Not yet, i'm going to try new beta in the next days, i'll let you know

@retlehs
Copy link
Sponsor Member

retlehs commented Jan 13, 2017

please keep the support back-and-forth on the discourse thread for this specific issue:

i'm locking this issue. please use the discourse topic for discussion:

https://discourse.roots.io/t/sage-9-beta-1-not-inserting-styles-in-browsersync/8525

@roots roots locked and limited conversation to collaborators Jan 13, 2017
@retlehs
Copy link
Sponsor Member

retlehs commented Jan 19, 2017

fixed in beta 2

@retlehs retlehs closed this as completed Jan 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants