Nice write up Sam! Yeah, with preact/compat you could still use React router, but if the preact router suited your needs, all good.
For the className prop, you can use either class or className in Preact. If you wanted to standardize it in your code, you could probably find an eslint rule for that.
There's a lot of talk about moving away from bundlers, so something, so htm is interesting.
Although, not Preact specific, Luke Jackson, from Formidable labs has been doing some interesting work. Their post, Don’t Build That App!, is a great read and uses the htm package like you demonstrated.
And thanks for the specific notes and the link to the article too--it was a great read, and I really appreciated both the step-by-step walkthrough and the added background on htm.
(I'm off to fix the class/className thing now, I knew I was missing something!)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice write up Sam! Yeah, with
preact/compatyou could still use React router, but if the preact router suited your needs, all good.For the
classNameprop, you can use eitherclassorclassNamein Preact. If you wanted to standardize it in your code, you could probably find an eslint rule for that.There's a lot of talk about moving away from bundlers, so something, so htm is interesting.
Although, not Preact specific, Luke Jackson, from Formidable labs has been doing some interesting work. Their post, Don’t Build That App!, is a great read and uses the
htmpackage like you demonstrated.Looking forward to your next post!
Thanks so much Nick!
And thanks for the specific notes and the link to the article too--it was a great read, and I really appreciated both the step-by-step walkthrough and the added background on htm.
(I'm off to fix the class/className thing now, I knew I was missing something!)