[Roadmap] Semi-formal ulid/ulidx convergence plan #110
Description
Hello! I've been lucky enough to have been granted maintainer access to this repository in order to modernise it, update its dependencies, merge/handle its feature requests and oversee its "rebirth" so to speak. It seems a lot of files haven't been touched in almost 8 years, so there'll need to be a bit of a refresh going forward.
I've started a plan/discussion over on ulidx (my repository/fork) to kick things off.. Please feel free to chime in and help figure out how these two libraries should converge, if they even need to. I won't elaborate here too much as 1 thread is enough, but the initial idea was to make this repository the primary, feature-rich library, and ulidx a smaller/leaner build following the same format guidelines. Though all of that remains to be seen.
I'll be closing issues/PRs that no longer align with the direction of the repository, or are simply outdated or likely to be covered in a future update/refactor. I'd like to state here that I intend to maintain and improve on the quality of this library, so it'll not only be safe to use in the future, but desirable to do so (over other alternatives, including bloated uuid libraries). Please don't take offense if I close an issue or PR of yours - I'm happy to discuss if you disagree - it's just a bit of house cleaning before doing a larger overhaul on a new major version.
Right now I'm without npm access - so I can't do any releases until that's solved - but I can get it ready for the first update in years 🎉