Prompt option: setup critical CSS inlining about quasar-app-extension-ssg HOT 2 CLOSED

Initially i didn't want to make the extension too opinionated. But after thinking of it, users could disable this feature then do it themself the way they want, with the library they want.

For memory leaking issue, we could generate critical CSS every time a page is rendered before writing it to a file. Instead of doing it after all pages have been generated.

What do you think about that ? @IlCallo

from quasar-app-extension-ssg.

Initially i didn't want to make the extension too opinionated. But after thinking of it, users could disable this feature then do it themself the way they want, with the library they want.

I meant that you could automatically add the code you provide in the README if the user select that feature into prompts, but baked in support is good too, I don't really have an opinion on this right now

For memory leaking issue, we could generate critical CSS every time a page is rendered before writing it to a file. Instead of doing it after all pages have been generated.

Unluckily, I don't have much experience in this field too... Are there cases where you do need to have all files processed to calculate the critical CSS? If not, I guess doing it on a "per file" basis could speed up the generation

from quasar-app-extension-ssg.