The dir '/dist/styles' disappears after 'yarn start', but is present after 'yarn build'. Why?

knowler · May 16, 2018, 2:59pm

I gotta dash, but since I put time into this, here is my half-baked answer:

So your issue is only happening during development (yarn start). Sage uses Webpack for it’s development build/watch process. A feature of Webpack is called Hot Module Replacement, which “exchanges, adds, or removes modules while an application is running, without a full reload.” Your styles are considered to be a module. So when it detects a change, it will get the new styles. However, it doesn’t compile a new stylesheet.

The 404 error is expected when HMR is running. This is where the “styles” that HMR is injecting are:

You’ll also notice the hot updates that HMR is receiving:

Perhaps, the best way to understand this is to simply obeserve it in action. Run yarn start, open up dev tools and watch what is happening to the stylesheet reference at the end of the head and the hot updates in the network tab when you make a change to the stylesheets.

Add notes about in-memory file system

opened 02:10AM - 17 Oct 16 UTC

closed 03:36AM - 13 Oct 18 UTC

QWp6t

sage

A common confusion among users is that certain files aren't written to the files…ystem during development. We can help clarify things by explaining to users that webpack-dev-middleware uses an in-memory filesystem. > The webpack-dev-middleware is a small middleware for a connect-based middleware stack. **It uses webpack to compile assets in-memory and serve them.** When a compilation is running every request to the served webpack assets is blocked until we have a stable bundle. https://webpack.github.io/docs/webpack-dev-middleware.html We could maybe research a plugin that will write the in-memory filesystem to disk anyway, such as: https://github.com/gajus/write-file-webpack-plugin

github.com/roots/sage

Address or document 404 on stylesheet during development

opened 05:33PM - 05 Nov 17 UTC

closed 07:17PM - 18 Jun 19 UTC

retlehs

i believe that the only place we've talked about how it's currently expected tha…t there is a 404 on `main.css` during local dev is on roots discourse. it's not on the docs or the readme related discourse threads: https://discourse.roots.io/t/consequences-of-absent-main-css-with-yarn-start-sage-9/10755 https://discourse.roots.io/t/sage-9-main-css-404-on-devurl/9799 - [x] I've read the [guidelines for Contributing to Roots Projects](https://github.com/roots/guidelines/blob/master/CONTRIBUTING.md)