Type "session" has no properties in common with type 'ICachingProps'

[joxicraft]

[{
"resource": "/C:/code/spfx-pnp-js-example/src/webparts/pnPjsExample/components/PnPjsExample.tsx",
"owner": "typescript",
"code": "2559",
"severity": 8,
"message": "Type '"session"' has no properties in common with type 'ICachingProps'.",
"source": "ts",
"startLineNumber": 92,
"startColumn": 52,
"endLineNumber": 92,
"endColumn": 61
}]

I need help with this error ... NooB

EDIT: WORKAROUND: Commented out the line spCache and replace the cache object in the IRespnseItem[] line 94 spCache = spfi(this._sp) and works fine, but the speed seems compromised

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4b19eb96-192d-2d8b-8d4e-0de787f22093
• Version Independent ID: e2cbd2b2-8bb7-a95f-0768-15f1b045b4c4
• Content: Use @pnp/sp (PnPJS) library with SharePoint Framework web parts
• Content Source: docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
• Product: sharepoint
• Technology: sharepoint-framework
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[AJIXuMuK]

@joxicraft - thank you for reporting this one.
The documentation is outdated and shows how to use PnPJS v2, not v3.

[GirishGulve]

@joxicraft
Got below solution at SharePoint Stackexchange and worked form me.
https://sharepoint.stackexchange.com/questions/301746/error-while-following-microsoft-documentation-on-web-part-caching-with-pnpjs.
import { Caching, ICachingProps } from "@pnp/queryable";

// ...

const cacheProps: ICachingProps = {
store: "session"
};
const spCache = spfi(this._sp).using(Caching(cacheProps));

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.