-
Notifications
You must be signed in to change notification settings - Fork 101
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
[question] can we run critters after export? #42
Comments
Hey, we can only run Critters within the build process. There's no other place to put it since it's a webpack plugin. Were you seeing an issue? Why do you think it should be elsewhere? |
Hey, What about using prerender-loader to produce the HTML files ? Would it be a good idea? Furthermore, the critters github page says:
|
You can use Critters already works, as is, with You can verify it's working by viewing the source of your built pages. A lot of CSS will be inlined in the |
@lukeed it seems the css generated by critters is not all the critical css. i will try to make a minimal example to reproduce it. |
Great, thanks! If that's the case, it's likely an issue with Critters itself, but I'm happy to take a look & pass it along to Critters if needed. |
Hey, Thanks for the answer :) I personally don't have any issue with the |
From what I observe,
pwa export
will use chrome to pre-render all pages (default) with css classes and everything. So running critter after this point make more sense right?The text was updated successfully, but these errors were encountered: