Side note, Bower is a dying package manager. You'd get better results if you promoted the npm link over bower.
Side note, Bower is a dying package manager. You'd get better results if you promoted the npm link over bower.
Other reason: the syntax is more explicit, and already familiar to anybody who has used Maps [1]
I find your syntax a little confusing. It's not immediately obvious how I would set multiple cookies with different options, for instance.
[1] https://developer.mozilla.org/en/docs/Web/JavaScript/Referen...
I see, you could just call the same function few times with different options (preferred) as cookies(cookie1, opt1); cookies(cookie2, opt2); or concatenate them: cookies(cookie1, opt1)(cookie2, opt2); but this is arguably really strange syntax.
I will add more examples to the readme.md to make it more clear :+1:
When you use two distinct dependencies that subsequently have the same dependency but separate major releases, you may encounter breakage.
The author simply prefers Bower because of how it handles this problem differently than npm.
"Dying" is a bit strong, but there's no question that NPM is becoming the go-to choice for javascript development across the stack.
There are better alternatives available (NPM/PostCSS/vanilla.js to the above)
Anyway, I didn't really intend this library to be in-the-loop. I just did it because I couldn't find one I liked in 2016. Which is just nuts on itself. so I went all old-school and tried to keep cross-browser support high and make it simple. It took an hour to be done and a couple of them to test and document it (plus another couple of them for small details such as CDN, bugs/patchs/small features).
I prefer my screwdriver, that I have to open with another screwdriver.