-
Notifications
You must be signed in to change notification settings - Fork 24
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
normalize.css -> modern-normalize #48
Comments
Do we have an explicit include of normalize? I thought that was included by Tailwind itself? Is it possible to override with something else? |
Ouh, i think i made a mistake. There is a file that contains normalize.css comment, but everything below is not normalize at all - i got fooled :) I think you are right about Tailwind - it has normalize, and to be precise, modern-normalize that i proposed, so all good. Sorry for confusion. |
I think it may have started as normalize but then we customized it a bit (prefixed with |
@cannikin Organizational question:
|
TL;DR yes, but you're right in that we need to get better at moving the PRs we have forward. But still, if you want to improve something, by all means, please make a PR! |
Hello,
Have you thought about switching normalize.css to modern normalize?
Ive seen many modern projects switching, and it seems like the approach is pretty in line with your target group (devs usually dont use ie 11 nowadays :) )
Repo: https://github.com/sindresorhus/modern-normalize
The text was updated successfully, but these errors were encountered: