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.
Holster router
Lots of updates this week, I gave a presentation on Holster at the June LoFi meetup and published a new npm package. The meetup was at 1am for me, so not the best time to be trying to explain how Holster works! 😅 but it was great to be invited to speak and hear from others doing similar work. I've also been going back and watching previous LoFi episodes which are really interesting and great to see how much work is going on in the local first application space.
The npm package I've released is called holster-router and is an extraction of some of the work that went into RSStream. I've done that so I can re-use the same routes and user creation process in a new Holster based project that I'm about to start. RSStream uses the concept of invite codes to control accounts, but the new project will be more open than this, so the holster-router functions that are shared between these projects will allow for more than one way to create an account. The recent work that went into user storage limits should mean that sign-ups can be open without worrying about server storage. All the other routes for managing password updates and resets will be shared and the new project will add new routes to holster-router as the sign-up model for that is worked out.
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.
Holster router
The npm package I've released is called holster-router and is an extraction of some of the work that went into RSStream. I've done that so I can re-use the same routes and user creation process in a new Holster based project that I'm about to start. RSStream uses the concept of invite codes to control accounts, but the new project will be more open than this, so the holster-router functions that are shared between these projects will allow for more than one way to create an account. The recent work that went into user storage limits should mean that sign-ups can be open without worrying about server storage. All the other routes for managing password updates and resets will be shared and the new project will add new routes to holster-router as the sign-up model for that is worked out.