-
Notifications
You must be signed in to change notification settings - Fork 38
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
Any chance to upgrade critical to v4.0.0 ? #55
Comments
Hi @gigo6000 I have helped triage some PRs and answer issues, but I think the maintainer is indeed needed to sustain any forward momentum on this project (merging, tagging, publishing to npm) and I unfortunately don't have permissions for that. (or time if I did, as I'm managing a few of my own projects). Thus, I can't speak for the maintainer but I think it may be worth considering this project archived effectively. |
Hi @thescientist13 thanks for the reply, we're now moving way from this project, in our case we actually didn't even need to include Critical in webpack/ webpack mix, generating the css from a simple JS is enough. Here's an example just in case anyone lands here and is curious: https://gist.github.com/gigo6000/9743475d1eb13794af0a17830b2f8a5a |
Hi, is this project abandoned? or is there any reason to not upgrade to the latest critical version (
v4.0.0
)The text was updated successfully, but these errors were encountered: