UNDERCODE COMMUNITY

Full written tutorial

191 views10:31

194 views10:44

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑Hack COOKIES :
> A simple, lightweight JavaScript API for handling browser cookies

🦑FEATURES :

Works in all browsers
Accepts any character
Heavily tested
No dependency
Supports ES modules
Supports AMD/CommonJS
Useful Wiki
Enable custom encoding/decoding
< 700 bytes gzipped!

🦑𝓛𝓔𝓣'𝓢 𝓢𝓣𝓐𝓡𝓣:

1) git clone https://github.com/js-cookie/js-cookie

2) cd js-cookie

3) $ npm i js-cookie

4) Direct download
Starting with version 3 releases are distributed with two variants of this library, an ES module as well as an UMD module.

Note the different extensions: .mjs denotes the ES module, whereas .js is the UMD one.

5) Example for how to load the ES module in a browser:

<script type="module" src="/path/to/js.cookie.mjs"></script>
<script type="module">
import Cookies from '/path/to/js.cookie.mjs'

Cookies.set('foo', 'bar')
</script>

6) Not all browsers support ES modules natively yet. For this reason the npm package/release provides both the ES and UMD module variant and you may want to include the ES module along with the UMD fallback to account for this:

<script type="module" src="/path/to/js.cookie.mjs"></script>
<script nomodule defer src="/path/to/js.cookie.js"></script>
Here we're loading the nomodule script in a deferred fashion, because ES modules are deferred by default. This may not be strictly necessary depending on how you're using the library.

🦑Basic Usage

1) Create a cookie, valid across the entire site:

Cookies.set('name', 'value')

2) Create a cookie that expires 7 days from now, valid across the entire site:

Cookies.set('name', 'value', { expires: 7 })
Create an expiring cookie, valid to the path of the current page:

Cookies.set('name', 'value', { expires: 7, path: '' })
Read cookie:

Cookies.get('name') // => 'value'
Cookies.get('nothing') // => undefined
3)
Read all visible cookies:

Cookies.get() // => { name: 'value' }
Note: It is not possible to read a particular cookie by passing one of the cookie attributes (which may or may not have been used when writing the cookie in question):

Cookies.get('foo', { domain: 'sub.example.com' }) // domain won't have any effect...!

4) The cookie with the name foo will only be available on .get() if it's visible from where the code is called; the domain and/or path attribute will not have an effect when reading.

🦑 Delete cookie:

Cookies.remove('name')
Delete a cookie valid to the path of the current page:

Cookies.set('name', 'value', { path: '' })
Cookies.remove('name') // fail!
Cookies.remove('name', { path: '' }) // removed!
IMPORTANT! When deleting a cookie and you're not relying on the default attributes, you must pass the exact same path and domain attributes that were used to set the cookie:

Cookies.remove('name', { path: '', domain: '.yourdomain.com' })
Note: Removing a nonexistent cookie neither raises any exception nor returns any value

✅Tested

@UndercodeTesting
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

GitHub

GitHub - js-cookie/js-cookie: A simple, lightweight JavaScript API for handling browser cookies

A simple, lightweight JavaScript API for handling browser cookies - js-cookie/js-cookie

213 views11:38