nabanitasarkar.com
Software developer focused on frontend engineering. I also dabble with design from time to time.
23 posts
20 followers
97 following
Regular Contributor
Conversation Starter
comment in response to
post
Perfect promotion xD. Will try in a new project for sure
comment in response to
post
That's right. I thought react router deprecated the declarative component, when I couldn't find in latest documentation. (Need to go through react router new changes).
comment in response to
post
Yes. Do do something with data. Show a toast message etc
comment in response to
post
What I am doing for the success handling, I am not sure if there is any caveat from tanstack query side. As in queryFn not remaining pure functions? @tkdodo.eu
comment in response to
post
I used useEffect today for a case where I had to show a toast and redirect to different route if there is error.
In similar success case, these days I directly put those login within the queryFn. Thus queryFn doesn't remain pure function though. (because of navigate from useNavigate)
comment in response to
post
Ya on that note you are right. But that's a totally different thing. Changing db in existing project is not feasible
comment in response to
post
That's what mongoose is for — to enforce the schema
comment in response to
post
I did the whole Gatsby to Next js hoola hoop. Finally a few weeks back, as I was transitioning to bluesky, decided to transition my website to Astro as well. Such a joy to use!
comment in response to
post
I also has same experience and complaint about Next.js . The situation became so bad, I went back to write plain HTML for 10-12 page sites. Tinkered with ejs and vite together as SSG solution. Finally I am happy now with Astro
comment in response to
post
Did it a few weeks back. Such a relief!
I am pushing for Astro even in my professional setting
comment in response to
post
Absolutely agreed. Once went deep into the rabbit hole with slate.js then with lexical. Finally thinking of trying prosemirror. Tiptap is probably good enough for small feature set
comment in response to
post
Already using
comment in response to
post
Can understand the "if it isn't broken, don't fix it". In that case, in newer company projects you can try maybe, if possible obviously.
comment in response to
post
And thank you so much for all your hard work 🙏🏻 I have been using vite in production for more than 2years. And it has been nothing but joyous ride since day one
comment in response to
post
Was thinking about switching but a friend mentioned issues with google meet. And also having a primary browser means I am opening devtools in many random scenerios for whatever random reason. But didn't get used to the devtools yet. Maybe I will use it as my personal browser and other for work
comment in response to
post
Surely was a lurker before. In many posts I thought of commenting but backed out, just because of fear. Fear of bashing, waste of energy, unnecessary rage. And that has been the experience in all the social media. So far here everyone feels like chilling like in a beach vacation or neighborhood cafe