Frontend

nothing is more disappointing than a library providing only react support.

"nobody has time to make versions for each framework!"

not what we are asking and not what you should do even if you're able to. Just make a vanilla JS version and a react version.

This ends up being better for your library long term

This reminded me of a clever type-stripping compiler by Bloomberg Engineering

The clever part is the weird spaces on the compiled JS: "By leaving the code coordinates unchanged, we've eliminated the need to generate sourcemaps. There's no encoding and decoding locations. Error stack coordinates are always accurate"

https://github.com/o-az
—
https://x.com/awkroot

Facts. React Hooks should really be treated as its own programming language (an ecosystem-incompatible flavor of JavaScript).

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>

Agreeeeeed!
Hooks is a terrible way to expose an interface.

> "Just make a vanilla JS version and a react version."

And have the react version be a light hook wrapper around the Vanilla JS.

Also building vanilla library first will make framework-specific libraries better in every aspect

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

Had it with @privy when implementing SIWF recently. They do provide vanilla js lib library that is unstable and without proper documentation. Decided to implement it myself and it was definitely quicker than understanding their code and fearing things will break in the future.

yes thank you. I just need vanilla JS. It is not a big ask.