bugfix: react context

[p4dd9]

fix Collecting page data .TypeError: r.createContext is not a function during build process Error: Failed to collect page data for /_not-found

Steps to reproduce

• open root dir
• run npm run build-netlify
• should fail build

It seems to be related to ReactContext used in a servercomponent

To investigate Providers using createContext:

• [x] ThemeProvider
• [x] IpInfoProvider (deleting IpInfoProvider.tsx resulted in no improvement
• [x] LanguageProvider (replace with https://nextjs.org/docs/pages/building-your-application/routing/internationalization https://nextjs.org/docs/pages/building-your-application/routing/internationalization#non-dynamic-getstaticprops-pages ?)
• [x] Sometimes Failed to collect page data for XXX XXX displays different pages by now and then (race condition? async?)
• [x] Does it build if streamer singleview pages with wishes is deleted? -> YES! --> Does it build if not_found is re-added -> YES! --> Does it build if [streamer]/[wish]/page.tsx without content.tsx is re-added -> NO!

[p4dd9]

https://github.com/pacocoursey/next-themes/issues/152

[p4dd9]

https://github.com/vercel/next.js/issues/41958

[p4dd9]

https://github.com/styled-components/styled-components/issues/1589 porting to styled components 6

[p4dd9]

https://github.com/styled-components/styled-components/commit/8766ec3909ac3fc7d82b00599e1509449b386464#diff-6947e143cd7ea9a496f1403ef3851a643e9775a3439bfd58d615155c62f48176

[p4dd9]

upgrading to styled-components 6 leads to

- info Collecting page data .TypeError: u.default.createContext is not a function

[p4dd9]

`Good to know:

To use an async Server Component with TypeScript, ensure you are using TypeScript 5.1.3 or higher and @types/react 18.2.8 or higher.`

https://nextjs.org/docs/app/building-your-application/data-fetching/fetching#async-and-await-in-server-components

[p4dd9]

https://nextjs.org/docs/getting-started/react-essentials#context

[p4dd9]

it is related to either page.tsx or its import for singleviews

[p4dd9]

issue seems to be related to smth else, in PR no dynamic paths are built

[p4dd9]

react-dom.development.js:6779 Uncaught Error: Hydration failed because the initial UI does not match what was rendered on the server. at throwOnHydrationMismatch

`Warning: An error occurred during hydration. The server HTML was replaced with client content in <#document>.`

`arning: Prop `className` did not match. Server: "sc-hKgJyM kmzcAu" Client: "sc-gKsdJj GYJQf"`

[p4dd9]

[p4dd9]

https://github.com/charityroyale/webapplication/pull/103 learnings:

• 'use client' in layout and page will lead to issues putting 2 much business logic into the nextjs app directory concept

[p4dd9]

so far, only the upcomingstream grid is a bit "off the grid" (hah) - planing to finish soon