Aleksandr Hovhannisyan

@AustenLamacraft Thanks for letting me know! Fixed.

@muratcorlu It's certainly an interesting idea. One reason I might not do this is because it ties you down to that one repo, whereas imo your articles should be independent...

@haIIux Glad to hear that it helped, and good luck with learning web dev! Also, heads up in case you ever revisit this blog post: I realized that it's been...

@Crunchy409 Glad to hear that! Thanks for reading 😄

@hello-jeff Thanks! I haven't, no.

@equinusocio Yeah, unfortunately, that won't work as far as I can tell. You'll need to use a slot or render prop if the tag is being used for more than...

@lianulloa Yup! Like I mentioned above, if the rendered element needs to have any props passed to it, then a tag name won't work (because your click event's typing depends...

@surjithctly I've had to do that before too. You have two options: 1. The component accepts a `level` prop of `1 | 2 | 3 | ... | 6`. (Preferred.)...

@duongductrong Why not just pass the component with its props directly as a slot? ```jsx import Button from "...." function Parent() { return } ``` Then type `slotName` as `ReactNode`.

@alpersunter Fwiw, I've been going back and forth on this a bit myself. In fact, I recently updated my site to rely more heavily on utility classes, especially for stuff...