You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to use the SDK cache feature and running into an error with the following configuration. current package version is @contentstack/delivery-sdk": "4.3.0
TypeError [Error]: defaultAdapter is not a function
at <anonymous> (node_modules/@contentstack/delivery-sdk/src/lib/cache.ts:17:33)
at Generator.next (<anonymous>)
at node_modules/tslib/tslib.js:169:75
at new Promise (<anonymous>)
at Object.__awaiter (node_modules/tslib/tslib.js:165:16)
at handleRequest (node_modules/@contentstack/delivery-sdk/src/lib/cache.ts:12:14)
at Object.<anonymous> (node_modules/@contentstack/delivery-sdk/src/lib/contentstack.ts:97:30)
at Generator.next (<anonymous>)
at node_modules/tslib/tslib.js:169:75
at new Promise (<anonymous>)
When setting to use a different policy, another error arises.
TypeError [Error]: Cannot read properties of undefined (reading 'getItem')
at Object.getItem (node_modules/@contentstack/delivery-sdk/src/persistance/storages/local-storage.ts:36:25)
at PersistanceStore.getItem (node_modules/@contentstack/delivery-sdk/src/persistance/persistance-store.ts:64:32)
at <anonymous> (node_modules/@contentstack/delivery-sdk/src/lib/cache.ts:59:40)
at Generator.next (<anonymous>)
at node_modules/tslib/tslib.js:169:75
at new Promise (<anonymous>)
at Object.__awaiter (node_modules/tslib/tslib.js:165:16)
at handleRequest (node_modules/@contentstack/delivery-sdk/src/lib/cache.ts:12:14)
at Object.<anonymous> (node_modules/@contentstack/delivery-sdk/src/lib/contentstack.ts:97:30)
at Generator.next (<anonymous>)
The errors occur regardless of the storeType that is configured for the cache options. A sample of the stack config is
I am attempting to use the SDK cache feature and running into an error with the following configuration. current package version is
@contentstack/delivery-sdk": "4.3.0
When setting to use a different policy, another error arises.
The errors occur regardless of the
storeType
that is configured for the cache options. A sample of the stack config isThe text was updated successfully, but these errors were encountered: