ScottHamper
commented
4 years ago Pretty much,
I originally wrote this library at the request of a co-worker, and because I was looking for a project to do at the time. Since then, I've learned to hate doing anything related to JavaScript. When I'm writing a library, I want to focus on the API/implementation, not spend time making sure it will fit into X/Y/Z build system/environment (AMD, CommonJS, Node.js, Browser). I don't want to have to deploy every single release of my library to everyone's personal favorite package manager (NPM, Bower - though, do people even use Bower anymore? I have no idea, I've avoided this stuff for years). Dealing with JS and the entire ecosystem around it sucks.
Also, I honestly don't understand the use case for this library, which probably sounds funny coming from the author of it. But any cookies important for security should be marked HTTP only (making the library irrelevant), and other cookies should probably just be set via HTTP headers from a server response. Cookies exist as a way to send state to servers that otherwise have no way of differentiating one client from another, so using cookies entirely locally without involving the server seems like an abuse of the technology. Local storage exists now - it should probably be used instead for those use cases.
Along those same lines, I've never actually used this library in a project. Given that it's of no personal use to me, and the rest of what I mentioned above, I can't find the energy/excitement necessary to update the library or deploy new releases. But it's public domain! Feel free to grab the code and incorporate it into your own project, make whatever changes you want. It's yours. Good luck.
i don't see any update on this repo for a long time, is it dead?