Daniel Tschinder

All packages are now at secure versions and `npm audit` does not report any security issues anymore. The deprecated packages are something that we will also address at some point...

Had the same issue here locally with nextra 2.2.20 nextra-theme-docs 2.2.20 next 13.2.4 It helped to remove the `.next` directory. and restart `dev`

Would you be able to create a small reproduction example? So we can look at it?

I guess the best idea would be to integrate this into our main docs site, so having automation that takes data from this repo and updates the docs in netlify/docs....

As this dependency is only used in tests I would prefer to keep it. It has a bunch of convenient functions. I noticed though that `@netlify/build` has it listed under...

> and the `functions` field on the build settings The [docs](https://docs.netlify.com/functions/optional-configuration/?fn-language=js#directory-2) though say it should be this: ```toml [functions] directory = "my_functions" ``` maybe `[build] -> functions` is the old...

> > and the `functions` field on the build settings > > The [docs](https://docs.netlify.com/functions/optional-configuration/?fn-language=js#directory-2) though say it should be this: > > ```toml > [functions] > directory = "my_functions" >...

I solved all the review comments. I had to rebase because of conflicts, but all new changes are in separate new commits. starting with [chore: add test for cache](https://github.com/netlify/build/pull/4585/commits/a676e61c9337d6f58485aa216324bb9cd7e74bcd)

The config for edge functions is currently incorrect in the schema: - `excludePattern`, `excludePath` and `pattern` are missing from the schema - `path` is currently only allowed to be a...

glob v9 only supports Node.js 16 or newer. So we have to wait until we can upgrade.