* Don't use `cursor: pointer` for buttons by default
This is a pretty common expectation but as outlined in in #8961 isn't really right. We considered this a long time ago but it felt too against the grain at the time. These days though very UI-forward applications like [Linear](https://linear.app/) are using the default cursor for buttons and I think this trend will continue as more people become aware that `cursor: pointer` is meant for links.
Let's update our defaults here to help nudge people in this direction and make it more common. If people want to change this in their own apps, it's just a line or two of CSS to add to their projects.
* Update changelog
Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com>
This reverts commit c47e66613f1d1072f7a71278d2ebee090af3010c.
Node 12 reached EOL on 30 April 2022 after which there will be no more bugfix or security releases. This is one reason why `postcss-load-config` dropped support for Node 10 *and* 12. However, as we still support Node 12 in Tailwind CSS v3, we can’t upgrade to `postcss-load-config` 4.0.
Restrict the GitHub token permissions only to just what is required and make them read-only where possible.
Signed-off-by: neilnaveen <42328488+neilnaveen@users.noreply.github.com>
* Update deps
* Fix usage of postcss config file in standalone CLI
The config file created with `--postcss` would fail because we didn’t stub require to load `tailwindcss` or `autoprefixer` when we should.
* Update tests
* WIP
* Refactor
* Support variants with quotes in them
We have to have two regexes here because this is actually ambiguous in the general case. The regex that generally handles `[&[foo='bar']]` would incorrectly match `['bar':'baz']` for instance. So, instead we’ll use multiple regexes and match both!
* Update changelog
