hoodie VS js-cookie

I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.

Once the user is logged in, you may need to access information like the user's name, email, etc. Choreo sends this information encoded in a cookie (named userinfo) upon successful login. We can extract the information using a cookie parsing library. For this example, we will be using js-cookie library.

Interesting thread. If oracle were to send a cease and desist to everyone that uses "javascript" I would have received one years ago: https://github.com/js-cookie/js-cookie

You could just use something like https://www.npmjs.com/package/js-cookie

Have a look at js-cookie. Also, read this.

js-cookie might help?

Are you using js-cookie, this js-cookie, on the server?

So something like this... (I’ll be using this package to simplify the code)

This is a simple video start guide to see how to get, set and remove cookies using npm package js-cookie in react.