Jan Potoms

> Since when can a component be an async function? I guess since Next.js started supporting [React server components](https://react.dev/blog/2023/03/22/react-labs-what-we-have-been-working-on-march-2023#react-server-components). Assuming you're not looking for an exact date 😄

Actually, just noticed the same happens when rendering [lazy components](https://react.dev/reference/react/lazy) as children ```tsx const MyLazyComponent = React.lazy(() => import('./Component')); ```

> I think we should also check that propTypes.element works. ~If I understand the concept correctly, server components themselves can't pass the server/client boundary. Only rendered elements. So you might...

Proposing another option here from the backlog grooming session: we add some hotspots to the screenshot. Each has a popover with a short explanation, and clicking them reveals a code...

> It is generally too busy— too much information and interactions here. The pulsating buttons can be a bit distracting, and there’s too much text in each popover. > I...

> I was thinking we could be much simpler than this, and the screenshot code relation could be done purely by highlighting, in the image, what the code is touching...

> Does this make sense? Yes, we're aligned. It's exactly what I'd want, just with the right design-sauce over it 🙂.

I think we can put the `"types"` field first even. PR welcome

Can you try to enable `checkJs` in your `tsconfig.json`? For now the types are strictly internal, I'm not sure I want to introduce a build step at this point.

I'm hesitant releasing a feature without tests. If you're up for it you can add test logic after this: https://github.com/Janpot/microdata-node/blob/a0473b6f0e70f62653a6149f2fe1a5d900f1abd1/test/suite.spec.js#L36 where you run `toRDF` on the input, convert it to...