Neef Rehman

>Also is this a valid prop for all axis types? @ckifer it is a valid prop for any axis that extend `BaseAxisProps` which, as it stands, is only `xAxis` and...

@ckifer @nikolasrieble I've just updated this PR to fix conflicts, and move to an RTL/Jest test. I've also replaced the demo with a pair of stories, which should make the...

@ckifer Thanks! The pre-push failures I had were all lint related. It looks like the storybook file I added had some issues that my editor took a while to recognise!...

@bmoren thanks for the quick reply! Sadly I'm not very experienced with package development so don't think I'll be of any help here, but will take a look. Thanks also...

Thanks! That worked perfectly 🙌🏾

@ferezoz I'm currently running into the exact issue you are describing and seemingly the same issue as @zinnah1995. When running `next start` everything is working fine, however after `next export`...

@ferezoz Thanks for this! Just copied it over and it did indeed work. Since the issue is a lack of an `exportPathMap` I thought I'd also go one step further...

@FrancoTanzarella @mayowadavid @elisegriset92 I had the exact issue (with `next export`), and what worked for me was setting up an `exportPathMap`, or using `getStaticPaths` in the dynamic routes.

I've just come across this after having tried for a while to implement some basic modal stacking (kind of like [what can be seen here](https://shadcn-dialog.vercel.app/)). Not being able to set...

@snowystinger as I understand it, that context (and others ending in `StateContext`) are only used for reading values from parent components, and not for providing props to be merged into...