overkill_nvim VS js-cookie

Lol I started trying to see what that’d look like earlier this year: https://github.com/turboladen/init.rs. It works fine and loads pretty fast. Started by making https://github.com/turboladen/overkill_nvim, but stopped work after https://github.com/noib3/nvim-oxi showed up.

Well, IDK how interesting it is, but a couple months ago I started writing overkill_nvim (and a couple other supporting libs) to allow you to write neovim plugins in Rust—not using msgpack, but making calls directly to neovim via FFI.

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.