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
The way paged.js work is a bit different from the normal web, as it pull all the stylesheet into a couple of style element (after modifying them a bit).
This means that when we update a css, we need to have a full reload and not a css update, a proper full reload.
It looks like from here that the CSS doesnt trigger a reload.
would it be possible to add a config key to force a page reload, even on css update?
The text was updated successfully, but these errors were encountered:
i’m passing the value of the argv.cssforcereload to the browser before loading the client js, and check that value to trigger a css rebuild (or keep the previously working setup).
i’m a bit bothered because the linter did its own thing and made the commits a bit harder to follow. I couldn’t find any options for writing code styles @zachleat.
Did i completely missed it?
Tell me if you think that is worth a PR. (also, i assume that we’ll need to push that option to eleventy in a second movement).
We’re using paged.js to make PDF from the web.
The way paged.js work is a bit different from the normal web, as it pull all the stylesheet into a couple of style element (after modifying them a bit).
This means that when we update a css, we need to have a full reload and not a css update, a proper full reload.
It looks like from here that the CSS doesnt trigger a reload.
would it be possible to add a config key to force a page reload, even on css update?
The text was updated successfully, but these errors were encountered: