ecyrbe / stalier Goto Github PK

Add an option to set cache-control back to the caller when result is fresh (cache miss).

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @types/node to v20.12.2
• chore(deps): update dependency eslint to v8.57.0
• chore(deps): update dependency express to v4.19.2 (express, @types/express)
• chore(deps): update dependency reflect-metadata to v0.2.2
• chore(deps): update dependency typescript to v5.4.3
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency @types/cache-manager to v4.0.6
• chore(deps): update dependency @types/jest to v29.5.12
• chore(deps): update dependency @types/supertest to v2.0.16
• chore(deps): update dependency ts-jest to v29.1.2
• chore(deps): update dependency ts-node to v10.9.2
• chore(deps): update dependency eslint-config-prettier to v9.1.0
• chore(deps): update dependency prettier to v3.2.5
• chore(deps): update dependency cache-manager to v5
• chore(deps): update dependency supertest to v6.3.4 (supertest, @types/supertest)
• chore(deps): update github/codeql-action action to v3
• chore(deps): update nest monorepo to v10 (major) (@nestjs/common, @nestjs/core, @nestjs/platform-express, @nestjs/testing)
• chore(deps): update orhun/git-cliff-action action to v3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

When using POST, PUT, PATCH, DELETE, allow the following header :
X-Stalier-Invalidate

with the following parameters :

POST /content
X-Stalier-Invalidate: method=GET, url=/resources/id, match=exact

To allow to serve user centric data, stalier should support to add a callback that takes the Request as a parameters to allow upstream apps to inject their Key on per request basis.

app.use(stalier({
        cacheKey : req =>
         `${req.user.id}-${req.method}-${sanetize(req.url)}`
        }));

stale-while-revalidate rfc has support for stale-if-error.
So should stalier.