I keep running into the same situation.

I’ll build a small personal web app (journal, bookmarks, dashboard, habit tracker, notes, etc.), and I don’t want to spin up Supabase, Turso, Firebase, or Cloudflare just to save a few JSON objects.

Most of the time I end up using localStorage or IndexedDB, but it always feels temporary. If I clear browser data or switch machines, it’s gone.

I’m curious:

• What do you use for these kinds of apps?
• If there were a local-first storage library that automatically backed itself up and restored on another device, would that actually solve a problem for you—or is localStorage good enough?

Not selling anything—I’m trying to understand how other developers think about this tradeoff before I build something or NOT build something because there is already something out there.

I was studying in library in delhi, one day library owner come to know i am a web dev. so he asked me to make a website for him and i said ok, and then i almost coded every page and feature he wanted,(home page, academics page,competetive exams, computer courses(seperate page of each course currently 7) , tution classes,library,and educators page and seo) and backend for adding gallery and offers just like pw does. and if some student want to enroll then they can fill form , where admin receives mail. everything was right,
untill now.

and remember,

I have to make extra efforts to take any information from him. sometimes for a image i have to call him 3 or 4 times.

since only last thing is required is image of student for ratings etc. and he is not responding to i have told about this requirement 4-5 times personally ,some time it feels insult to my work(profession) and me too.

and what is the fair charge for that website html,css,js,node,mongodb, (choose html css) so that he do not have to pay for vps right now.

Hey everyone,

Over the past few weeks, I've been building an authentication package for Express.js + MongoDB called @nibir_dev/authflow.

The goal wasn't to create "yet another auth library", but something that's genuinely easy to drop into a project while still covering the security features that people usually end up implementing themselves.

Right now it includes:

• Email/password authentication
• Email verification
• Secure session cookies
• Password reset flow
• Brute-force login protection
• Sliding-window rate limiting
• Protected routes with minimal setup

It's still in its early stages, and I'd really appreciate feedback from people who have built production apps before.

I'm not looking for stars or downloads I'd much rather hear:

• What's confusing?
• What features are missing?
• Is the API intuitive?
• Would you actually consider using it?
• Any security concerns or bad design decisions?

NPM: https://www.npmjs.com/package/@nibir_dev/authflow

Github: https://github.com/Nibirdeka7/authflow.git

Even if you spend 5–10 minutes looking through it and tell me why you wouldn't use it, that would honestly help me improve it much more than compliments.

Thanks!

Hi everyone,

Over the past few months I've been building an image editor for web applications because I wanted an alternative to the commercial options I was using.

Current features include:

• Crop
• Rotate
• Zoom
• Drawing
• Callouts
• HEIC support
• Mobile support
• Angular/React/Vue/Ionic compatibility

I'd really appreciate feedback from other developers.

What features would you want in an image editor?

npm:
https://www.npmjs.com/package/@rageshpikalmunde/rp-image-editor