New Holster release focused mainly on concurrency fixes. I've been working on a new app that runs on Holster which is very front end heavy and running all sorts of async requests, and creating lots of tests for it at the same time. The tests started getting pretty complicated, matching the types of interactions involved, and these all run on top of real holster test instances. The tests started getting a bit flaky as they exhausted their memory limit and swapped out cache files.
I realized Holster has never had any specific concurrency tests, so it was interesting adding them and looking at what sort of race conditions were causing problems. I have to say that Claude is getting really good at methodically working through scenarios without getting lost in the details. I'm impressed with the way it found the issues that have been fixed in this release and the relatively simple changes that were made.
Holster browser
I've created another npm package that is complimentary to holster-router, this one is called holster-browser. It's another extraction of core utilities and components from RSStream so I can use them in other projects.
So now if you want to use Holster with Express and React, it's super easy to put them all together and have a working authentication system. Holster is still completely independent, but the other two side projects assume the same endpoints and account structures. I'll probably add to both as I need extra features and not worry so much about publishing the applications that use them.
Concurrency
I realized Holster has never had any specific concurrency tests, so it was interesting adding them and looking at what sort of race conditions were causing problems. I have to say that Claude is getting really good at methodically working through scenarios without getting lost in the details. I'm impressed with the way it found the issues that have been fixed in this release and the relatively simple changes that were made.
Holster browser
So now if you want to use Holster with Express and React, it's super easy to put them all together and have a working authentication system. Holster is still completely independent, but the other two side projects assume the same endpoints and account structures. I'll probably add to both as I need extra features and not worry so much about publishing the applications that use them.