3 commits

Author	SHA1	Message	Date
ChanHui	8d45aa9bfb	update @types/react version in examples (#57259) ... ### What? When I ran `npx create-next-app --example with-turbopack` and installed dependencies using `yarn`, I found an typescript error(`'SomeComponent' cannot be used as a JSX component.`). <img src="https://github.com/vercel/next.js/assets/51700274/f6c7e478-c0b1-4ea2-996f-4c0c78e3bb4b" width=400 /> and I realized that the bug is due to the version of @types/react(18.0.x). you can check this issue on [here](https://github.com/vercel/next.js/issues/42292#issuecomment-1594351684) too. ### Why? It seems that there is an error occurring in the @types/react version 18.0.x. ### How? It would be good to change the @types/react version to 18.2.8 in the next.js examples. I think this change will resolve [this issue](https://github.com/vercel/next.js/issues/55080#issue-1884846177) [NestJS documentation](https://nextjs.org/docs/app/building-your-application/configuring/typescript#async-server-component-typescript-error) also states to upgrade the version. Co-authored-by: Lee Robinson <me@leerob.io> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>	2023-10-26 19:52:08 -05:00
Ryan LaBarre	b436589ff8	Maintenance: minor example dep bumps to fix moderate vulns (#56375) ... ### What? Merged a bunch of dependabot alerts in my own canary branch, mainly postcss patch updates, and one graphql minor update, to fix moderate security vulnerabilities in examples. Spot checked most and look good still. EDIT: also one in scripts/send-trace-to-jaeger ### Why? Because safety ### How? Dependabot --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Steven <steven@ceriously.com>	2023-10-04 11:18:54 -04:00
Ivan Kiráľ	7c15278cc2	Upgrade librabries and rebranding kontent.ai (#45260) ... Co-authored-by: JJ Kasper <jj@jjsweb.site>	2023-02-06 13:21:52 -08:00

Renamed from examples/cms-kontent/package.json (Browse further)