Bug report

Describe the bug

Emotion 11 throws an error during the compilation.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Clone https://github.com/vercel/next.js/tree/canary/examples/with-emotion
2. Run yarn dev

Expected behavior

It should work.

Screenshots

kolle-on-xps :: moving-cities/with-em

Describe the bug
I have a release-date field with a custom date_format set to DD-MM-YYYY, so something like:

name: 'release-date'
label: 'Release date'
widget: 'datetime'
date_format: 'DD-MM-YYYY'
format: 'DD-MM-YYYY'

Then I have release-date set under sortable_fields, which gets recognized, but doesn't quite work as expected.

Expected behavior
I would exp

As we attempt to pick up the release cadence, we are in need of an explicit changelog file which enumerates changes in each version. This should be a markdown or plaintext file adhering to some form of standardized format. Ideally, it will be able to work with #582.

There are 3 "examples" for dynamic (client side) routing, 2 in the docs (guides) and one is a template.

The 2 guides in the docs are technically working, but they do not use addPrefetchExcludes.

• dynamic-routes-reach-router.md
• [docs/guides/dynamic-rou

I don't really know Tokio or the best way to upgrade it, if someone has time to do it it shouldn't take too long.

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo