louisjrdev
banner
louisjrdev.bsky.social
louisjrdev
@louisjrdev.bsky.social
Developer, Designer, IT Enthusiast, Maker, Husband.
louisjr.dev/rss.xml
Just a heads up the ssl is down for lgtm.shop
lgtm.shop
November 20, 2025 at 5:07 PM
chrome dev tools mcp or playwright mcp
October 15, 2025 at 4:41 PM
I’m intrigued by what you mean with this, as in you can proxy to a python api or as in you can use whatever js server you want express etc?
December 3, 2024 at 5:05 PM
oh damn! thats nice
November 25, 2024 at 5:24 PM
Great idea for the Christmas lists!
November 25, 2024 at 5:22 PM
I think I have, but I am working in an nx monorepo at the day job and it doesn't play nice with that setup unfortunately😕
November 22, 2024 at 3:40 PM
Two downsides with Neovim where VSCode is much better is, I haven't managed to get a jest test runner and debugger working as smoothly in Neovim and multi-line find and replace. Thats when I will open a VSCode window, but thats not too often that its an issue.
November 22, 2024 at 3:28 PM
Also I use Neotree and it knocks spots off of the VSCode file tree, in terms of keyboard accessibility.

Great plugin though, if you aren't as picky as me with the config its probably a great thing to try out.
November 22, 2024 at 3:28 PM
I have actually tried this! It gets you most of the way, but I have my leader mapped to space in Neovim and I was finding I was having to set lots of custom bindings to stop VSCode waiting for a command when i was normally typing spaces in inset mode, or in search etc.
November 22, 2024 at 3:28 PM
I made the same switch from VS Code => Neovim a while ago, I think for me its lighter weight, faster, much more customisable and it only has the functionality I need. Dealbreaker is fully keyboard navigable UI with completely custom keybinds, couldn't replicate that as nicely in VS Code.
November 22, 2024 at 3:19 PM
Nice work!
November 20, 2024 at 1:11 PM
Would you be able to clarify a bit further on what's happening in this demo? Not fully sure what I am looking at there regarding the cause of the memory leak.
November 20, 2024 at 12:59 PM
Yeah that's why we opted for them, keep our UI responsive whilst we wait on some number crunching, in our case a lot of financial data.
November 20, 2024 at 12:58 PM
Just knowing about Web-Workers is half the battle, there is probably a lot of sites out there that could make use of it, if they knew about it.
November 20, 2024 at 12:48 PM
another way around that too, if you need the persistence, is writing and reading to IndexedDB, and if you do that, save yourself some sanity and use github.com/jakearchibal... from @jakearchibald.com
GitHub - jakearchibald/idb: IndexedDB, but with promises
IndexedDB, but with promises. Contribute to jakearchibald/idb development by creating an account on GitHub.
github.com
November 20, 2024 at 12:46 PM
Yes absolutely, if I knew now what I did when I started, I would have made our data structures differently to nicely sit within one of those. Will probably require some refactoring for optimal compatibility at this point 😄
November 20, 2024 at 12:42 PM
This is where comprehensive automated tests really helps out, not a 100% solve though 😅
November 20, 2024 at 12:40 PM