Recursive link checker (compared to the rust lychee)

• parse a phone number
• normalize a phone number to E164 from local phone number or international codes
• detect if the phone number is valid
• get the country code from a phone number

Another small compiler to add, substract, multiply and divide numbers

Stay close to the standard. Expose APIs instead of wrapping them.

The author asks for less HTML-in-JS and demonstrates it with the Next meta tags example.

Whenever a problem can be solved by native HTML elements, the longevity of the code improves tremendously as a result. This is a much less alienating way to learn web development, because the bulk of your knowledge will remain relevant as long as HTML does.

What's your favorite solution for not-quite-component components?

With those I mean components that are more boilerplates to be expanded upon, instead of actual ready-to-go components you just tweak a few details of. Components that would grow too complex if you'd need to account for all possible interaction and design versions through props or CSS custom properties.

I think often the alternative is composability: ie. what's the minimum functionality that the cookie consent component could have? Could it be a wrapper that provides cookie-setting functionality to whatever UI component it wraps? Could it be a little JS module different components could import to reuse?

A JS-Logger library

A great guide on the modulo operator :)

A qr code scanner library based on Open CV with the WeChat algorithm. A state of the art scanner, and maybe the best.

One advantage in svelte is that we can integrate JS libraries quickly

An other ready-to-production framework with an opinionated tech stack. Powered by Vercel.