Migrating SafelyRest from JavaScript to TypeScript

React developers sometimes face tricky behavior of React. For example: in some specific situations, same-name component-instances re-render each other, instead of doing a fresh independent new mount. This image shows this tricky situation and the solution which is the "key" prop of a component. The different "key" prop forces the component to behave independently even if it has the same name ("Item"). Tags: React, React.js, ReactJS, TypeScript, JavaScript, Zustand, Redux Toolkit, Tailwind, CSS, MUI, MaterialUI, ChakraUI, SVG, Portfolio: https://lnkd.in/dPq6PNuH

🚀 Day 30 – Future of JavaScript We started with basics… and now we’re here 👇 JavaScript is no longer just a browser language. It’s powering: ⚡ Full-stack apps 🌐 Edge computing 🤖 AI interfaces 📱 Mobile & desktop apps With tools like Next.js, TypeScript, and WebAssembly, the ecosystem is only getting stronger. 💡 The real takeaway? Don’t just learn JavaScript — build with it. Consistency beats intensity. 30 days down… but your journey is just getting started. #JavaScript #WebDevelopment #Frontend #Angular #TypeScript #CodingJourney #100DaysOfCode

🚀 Day 967 of #1000DaysOfCode ✨ useEffect Hook in React (Explained Simply) `useEffect` is one of the most powerful hooks in React — but also one of the most misused. In today’s post, I’ve explained the `useEffect` hook in a simple and practical way, so you can understand how and when to use it correctly. From handling API calls to managing subscriptions and syncing data, `useEffect` helps you deal with side effects in your components. The tricky part is understanding dependencies — which often leads to bugs like infinite loops or missed updates. I’ve also covered common mistakes developers make and how to avoid them in real-world applications. If you’re working with React, mastering `useEffect` will make your code much cleaner and more predictable. 👇 What’s the most confusing part of `useEffect` for you — dependencies or execution timing? #Day967 #learningoftheday #1000daysofcodingchallenge #FrontendDevelopment #WebDevelopment #JavaScript #React #CodingCommunity #ReactJS

Understanding State Management in React JS is a game changer for every frontend developer 🚀 From managing simple local states to handling complex global data, mastering this concept helps you build scalable and efficient applications. In this post, I’ve simplified: ✔ What is State ✔ How it works in React ✔ Local vs Global State ✔ Popular tools like Context API, Redux & Zustand If you're learning React, this is one concept you can't afford to ignore 💡 👉 Save this post for later & share your thoughts in the comments CODING OF WORLD #ReactJS #WebDevelopment #FrontendDevelopment #JavaScript

I still remember the old npm ritual: install a package → hit type errors → hunt down @types/* → repeat 😄 If you’re returning to JS/TS after some time, you’ll notice a big change… 👉 You don’t need @types as much anymore. So what changed? Over the last few years, the ecosystem quietly evolved: • Most modern libraries now ship with built-in TypeScript types • TypeScript is no longer “optional” — it’s the default • Tooling (Vite, tsup, etc.) makes generating types effortless • Newer runtimes are becoming more TS-friendly In short: 📦 Libraries now come “type-ready” out of the box You’ll still see @types/* for: – Older JS libraries – Node/test environments – Some community-maintained packages But the constant back-and-forth? Mostly gone. #TypeScript #JavaScript #WebDevelopment #NodeJS #DeveloperExperience #CodingLife #SoftwareEngineering

I Thought This Was Easy ! Date: 9/4/2026 Today, I tried another React.js project: Transfer List. When I saw it for the first time, I realized this is too easy—only a game with array, and state updates. 😎 But? When I tried it, I got stuck ! 🤣 🤣 The first two functionalities—moving all items from the left box to the right box and vice versa—I made easily. 😊 But moving only checked items was the most challenging part of this project.🤔 Disabling buttons based on conditions (most time-consuming). After making this project, what I learned: 👉 Improved logical thinking about states. 👉 I learned why the Double-Bang operator is important. 👉 Strong command of filtering. And from what I know, these are the weak areas where improvement is required: 👉 Controlled Components 👉 I always use useState; I need to practice useReducer more. Github Repo - https://lnkd.in/gK9cqYxm #ReactJS #WebDevelopment #CodingJourney #JavaScript #CodeNewbie

Build a Headless Expense Tracker to practice Typescript. I write pure Typescript functions to handle all the math and logic, and then connected it to a very simple Vanilla JS frontend. A few key things I learned and implemented during this build: - I stopped using long, messy chains of .filter() and learned how to use a single Array.reduce() to group and calculate my expenses cleanly. - I learned how to handle TypeScript's strict null-checking without making the app crash when building dynamic objects. Repo (mono): https://lnkd.in/d_2bTvvy #TypeScript #WebDev #LearningInPublic #JavaScript

🔥 JavaScript Devs — Check Data Before Using It Hey LinkedIn family 👋 Many bugs happen because we trust data too quickly. 💥 Example: user.name.toUpperCase() Looks fine… But if user is null? 💥 App crashes. 💡 Better way: ✔ Use optional chaining user?.name?.toUpperCase() ✔ Add default values ✔ Validate API data ⚡ Senior lesson: “Never trust data blindly.” Always check first. Have you faced this bug before? #javascript #frontenddeveloper #backenddeveloper #webdevelopment #codingtips #softwareengineering #js #cleanCode #programmingtips #seniordeveloper

Excited to share a new episode of Beyond Node.js ✨🎉 This time, we sit down with Ulises Gascón — TC39 delegate and maintainer of widely used JavaScript tools — to talk about what actually matters in production. We cover: • The worst things seen in real Node.js applications • Common misconceptions about Node.js in production • What teams should really focus on If you're working with Node.js in production, this conversation is for you. Watch the full episode in the comments 👇🏼 #Nodejs #JavaScript #Backend #SoftwareEngineering #OpenSource

⏳ 9 years. That's how long it took JavaScript to admit that new Date() was broken. Temporal just reached Stage 4. It's officially in ECMAScript 2026. Already shipping in Firefox and Chrome. TypeScript 6.0 includes the types. V8 14.4 turned it on by default, which means the next Node.js major gets it native with no flag. 🔥 Why this matters JavaScript Date has been a joke since 1995. Month indexes start at 0. Mutation everywhere. No time zone support. DST math that silently lies to you. Every team has written a Date wrapper at 2am. Every project pulls in a 70KB date library. That era is ending. 🧠 What Temporal gives you • Immutable date/time objects. No more accidental mutations. • Built-in time zones. Real zones, not offsets. DST-aware arithmetic that works. • Clear separation of concerns: PlainDate, PlainTime, PlainDateTime, ZonedDateTime, Instant, Duration. Each type means one thing. • Non-Gregorian calendars supported natively. • No more "is this UTC or local?" guessing game. Before: const meeting = moment.tz("2026-05-03 10:00", "Europe/Paris"); const inNY = meeting.clone().tz("America/New_York"); After: const meeting = Temporal.ZonedDateTime.from({ year: 2026, month: 5, day: 3, hour: 10, timeZone: "Europe/Paris" }); const inNY = meeting.withTimeZone("America/New_York"); No clone. No mutation. No surprises. ✅ What you can delete from package.json • moment (deprecated for years, still installed everywhere) • date-fns (for most cases) • luxon • dayjs • that custom Date helper nobody wants to own Keep them if you ship to browsers older than 2025 or Node older than 26. Everywhere else, start migrating. What library are you killing first - moment, date-fns, or that hand-rolled Date util in your repo? 👇 #javascript #typescript #nodejs #ecmascript #temporal #webdev #frontend #backend #tc39 #fullstack