Anyway, I found this npm fetch-cookie that solves my use case. However I still think it would be cool to have a fetchEvent that modules like fetch-cookie can hook into instead having to decorate it like he did

It could be used for authentication strategies in all request for a rest-api
If you were to use node-fetch as a proxy then it would be easy to just add cors headers to all response
if you want to decode/encode a different content-type (say googles Protocol Buffers application/protobuf) then it could be as easily as to just hook it into a fetchEvent
You could write your own network logger using fetchEvent instead of having to do it everywhere in the code
You could write your own cache mechanism that caches stuff and you would only have to write it once

think:

const fetch = require("node-fetch")
const fetchCache = require("fetch-cache")
const fetchDebug = require("fetch-debug")
const fetchCookie = require("fetch-cookie")({expire: '1Day'})
const fetchCompress = require("fetch-compress")
const fetchJpegTranscode = require("fetch-jpeg-transcode")

// this would be applied for all request being made
// super useful if you don't want to make it everywhere else in the code
fetch.on('fetch', fetchCookie)
fetch.on('fetch', fetchCache)
fetch.on('fetch', fetchJpegTranscode)
fetch.on('fetch', fetchDebug) // logs all request url,statusCode and time it took for all request

fetch('/login') // saves a cookie
fetch('/images/profile/hash.jpg') // would be transcoded to another format
fetch('/images/profile/hash.jpg') // would load from cache and wouldn't need transcode
fetch('/logout') // clears the cookie

Uh oh!

cookie jar #94

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions