What version of Next.js are you using?

11

What version of Node.js are you using?

v14.17.0

What browser are you using?

Chrom

What operating system are you using?

MacOs

How are you deploying your application?

next start

Describe the Bug

When i use the with-zustand example, it throws this :

Provider initialStore is deprecated and will be removed in the ne

Describe the bug

The markdown widget currently defaults to serializing links as autolinks if possible, i.e. [https://example.com](https://example.com) will be serialized as <https://example.com>. This is the default behavior of remark-stringify (and an option to change this behavior only exists in newer versions of remark-stringify).

Unfortunately, autolinks are [not compatible w

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

The main issue is that it's painful to get a real library loaded without just creating some files and commit them. Ideally there would be a function/macro that can be used to create pages/sections.
The other files in the library component create whatever is needed manually but it makes tests very verbose/long where 90% of the test is actually setup.
The library.rs really needs some more tes

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