Page-level presence

[filipesilva]

No description provided.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/athens-research/athens/8svBxySYWGA99AWY1EyKrC7xjULh
✅ Preview: https://athens-git-fork-filipesilva-presence-details-athens-research.vercel.app

[neotyk]

LGTM

[tangjeff0]

Not sure if this is a known issue. I'm guessing this can be addressed in a future PR.

[filipesilva]

@tangjeff0 it's known, some of the in-concept elements (like blocks) have erros like this on storybook. Avatar is being used right now but that particular story uses blocks as well. IIRC @shanberg was going to fix those comps that error on storybook.

[tangjeff0]

Great work @filipesilva @shanberg !

[tangjeff0]

Can you provide some context on why Babel was imported in this PR? Just curious @filipesilva

[filipesilva]

@tangjeff0 we were already using babel, but with a different config (.babelrc instead of babel.config.js). Trying to use to use the more complex presence components revealed issues with the babel setup that required a change in config type (to add functions) and change in configuration items (to fix the issues proper).

For futher context, storybook itself also uses babel for TS compilation, and shadow-cljs uses babel for node_modules compilation from ESM to CJS.

[shanberg]

Not sure if this is a known issue. I'm guessing this can be addressed in a future PR.

I do plan to fix, just lower priority.