Buttons are for submitting forms and nothing else.
In HTML a link is created using an <a> element.
React has a <Link> element for this purpose, it will be rendered as <a>.
Please OP, at least try to learn a little bit about the underlying technologies.
Also, React does not have a Link element. Please at least try to learn a little bit about the underlying technologies.
Into the trash it goes.
It's a tradeoff. If you roll your own password flow, you need to add MFA to be secure. The complexity of what you need to build and maintain goes up.
A simple magic link flow for an app like this, where you are really only likely to log into it once per project you start.
Personally though, I also use a password manager. And I am annoyed enough by email magic links, that any of my personal projects will at least have a passkey implementation.
So I agree they're annoying. But they're definitely not "dumb". They're a tradeoff. This developer has chosen his own time over user convenience; which is a common tradeoff for small developers.
Also yes they're super annoying for the user too. It's inconvenient and less secure.
Passkeys are awesome, yeah.
This whole discussion started when @meindnoch wrote ">Sign in or create an account with your email. Into the trash it goes.".
I think magic links are acceptable for a small solo developer project. Expecting a solo developer so shoulder the burden of rolling their own auth, paying for an auth service, or self-hosting an containerised auth-service and wiring their application to it is a bit much for a tiny project like this.
Anything more than a small solo project should graduate to a better solution- I hope we can all agree with that.
Unless you mean to say I should set up 2FA for my CSS theme variable helper website?
Passkeys and OAuth/social login are great, but everyone has an email. And I don't think any mainstream site supports only passkey as an auth method (and no other way).
big tech is only allowing Social login from another big tech anyway, they use whitelist and banning everyone that dont use that because they cant guarantee untrusted "third party"
True, every login must be standardized around social auth and oauth2
edit: would also love to be able to open preview on new tabs with middle-click.
Tweakcn also charges $ users to be able to share and save themes which I think is silly for a tool like this, should be 100% free and open source.
I also prefer the simple UX of ShadcnThemer better but I'm biased of course.
this is why ecosystem that stable like Go is better for vibe coding
Footer links:
GitHub repo https://github.com/miketromba/shadcn-themer
Three other links also in the footer but they only bring me to login screen:
Terms of Service https://shadcnthemer.com/terms
Privacy policy https://shadcnthemer.com/privacy
Contact https://shadcnthemer.com/contact
Not sure why this upsets people, is it because it's popular and therefore bad?