Search for a command to run...
Software Developer (Full Stack) with 4 years of experience building scalable web applications across frontend and backend. Focused on performance, security, and clean architecture. Skilled in troubleshooting, agile collaboration, and delivering production-ready solutions. Driven by continuous learning and delivering high-value, user-centric solutions.
No comments yet. Be the first to comment.
If you juggle personal projects on GitHub and company work on Bitbucket, you’ve probably run into this: You push your work code, and Bitbucket says — "This user cannot be matched to an Atlassian account." Why? Because Git is still using your person...
So, you've just dived into the world of Linux and you're itching to get your hands on some cool software. Fear not, fellow penguin enthusiast! In this guide, we'll explore five hassle-free ways to install applications on your Linux machine, using eve...
Discover the simplicity of Docker with our guide on "No-Nonsense Docker Commands for Developers." Streamline your container workflow effortlessly and boost your development game with straightforward, practical instructions. Build Image : Build an ima...
Unlock layout flexibility with min-width: 0 in your CSS toolkit. Tread carefully to avoid unintended layout surprises. Enhance responsiveness, but respect default styles for a harmonious design dance. 🚀 Pros of min-width: 0 for All (*) Flexy-Flex L...
Some Ordinary Developer
10 posts
A not-so-ordinary tech blog
Modern web applications often rely on authentication tokens stored in the browser's localStorage to manage user sessions. During development, teams frequently work across multiple environments—such as a deployed development server and a local localhost instance.
A common workflow challenge arises:
Developers must log in to the development environment, manually copy the access token from localStorage, and paste it into the local environment's localStorage to authenticate their local React app.
This process is:
Repetitive: Every time the token expires or a new session is needed, the process must be repeated.
Error-prone: Manual copying and pasting can lead to mistakes, such as copying the wrong value or pasting into the wrong key.
Time-consuming: Interrupts the development flow and wastes valuable time.
To address this pain point, our team built the LocalStorage Sync Chrome Extension.
Try it out:
Clone the LocalStorage Sync Browser Extension, load it into Chrome, and streamline your development process today!
Configure Once:
Set the source environment URL (where you're logged in), the target environment URL (your local app), and the localStorage key (e.g., access_token) in the extension popup.
One-Click Sync:
Click "Sync Now" in the extension. The extension:
Reads the token from the source environment's localStorage.
Writes the token to the target environment's localStorage.
Reloads the target tab so your app picks up the new token.
No More Manual Steps:
No more opening DevTools, copying, switching tabs, and pasting. The extension automates the entire process.
Saves Time: Reduces a multi-step manual process to a single click.
Reduces Errors: Eliminates mistakes from manual copying and pasting.
Boosts Productivity: Lets developers focus on coding, not on repetitive setup tasks.
Easy to Use: Simple configuration and persistent settings for repeated use.
If your team is tired of manually syncing authentication tokens between environments, the LocalStorage Sync Chrome Extension is a simple, effective solution.
Automate the tedious parts of your workflow and get back to building great applications!