You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I change styles.sass and save, the page refreshes properly. But on the second edit of styles.sass the page no longer refreshes from the styles file. Does fine with updates to the template file itself and other files, but not from styles.sass.
I'm guessing this is because of how the styles are added to the template page on the Twitter Bootstrap Jade template:
From /src/layout/default.html.jade above "body"
- var styles = getBlock('styles')
...
- styles.add(["/vendor/prettify.css"])
...
- styles.add(["/styles/style.css"])
...
Then within "head"
!= styles.toHTML()
Is this not a valid way to include the styles? Or is there some way we can pick up on this and still refresh after the first one? Or, is it something else entirely that I can tweak to fix.
The text was updated successfully, but these errors were encountered:
I believe this is an issue with the watchr dependency. I've updated watchr a few months ago, but the change needs to make itself into DocPad. Issue for that is over at docpad/docpad#1045
Actually, does DocPad perform the regeneration, but the livereload plugin just fails to auto refresh the browser? If DocPad doesn't perform the regeneration, then probably the watchr issue, if it is the later, then it is a livereload issue.
If I change styles.sass and save, the page refreshes properly. But on the second edit of styles.sass the page no longer refreshes from the styles file. Does fine with updates to the template file itself and other files, but not from styles.sass.
I'm guessing this is because of how the styles are added to the template page on the Twitter Bootstrap Jade template:
From /src/layout/default.html.jade above "body"
...
...
...
Then within "head"
Is this not a valid way to include the styles? Or is there some way we can pick up on this and still refresh after the first one? Or, is it something else entirely that I can tweak to fix.
The text was updated successfully, but these errors were encountered: