Closed HasanKaragulmez closed 11 months ago
Hi @HasanKaragulmez, We thought we fixed this particular problem, however it seems not, apologies! I already have a fix locally and will release the fix as soon as its been reviewed. I'll keep the issue open until we have verified this solves your problem.
2- The relevance-function is referenced as only being an Express helper (and we don't use Express, and, neither seems the Bloomreach NextJS example). Is the relevance SDK-call not actually dependent on Express, but always mandatory when supporting Relevance?
No the 'express' module is not actually depending on express. I just provides a function that can be used in middleware on the server. I guess we could rename that path.
This is fixed in 22.0.x
Hi, when upgrading to SDK 21.0.0 after 17.1.1 (due to async-issues), notably, https://github.com/bloomreach/spa-sdk/issues/7 - I've now found that the relevance-import example seems broken.
I've got multiple questions regarding this:
1- it seems mandatory that this relevance-sdk call gets executed, due to it setting the _v cookie.
The following error occurs, when trying to import the relevance function with SDK version 21.0.0
The NextJS (which we use) example here also trails behind the current changes, see relevance call here: https://github.com/bloomreach/spa-sdk/blob/e253082582192b5b784be005a1d27e53ef16002e/examples/next/pages/%5B%5B...route%5D%5D.tsx
as it's not updated to use the SDK 21.0.0, which is imperative for us to use do to the async-reverts in 21.0.0.
Is there a new way of calling this, introduced with the cjs changes? What is the correct way?
2- The relevance-function is referenced as only being an Express helper (and we don't use Express, and, neither seems the Bloomreach NextJS example). Is the relevance SDK-call not actually dependent on Express, but always mandatory when supporting Relevance?