feat: adding redis APL

[JannikZed]

this PR is used to bring native redis support as APL. It is fully tested and working.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3fa3866

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@saleor/app-sdk	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[krzysztofzuraw]

Good job 👏🏻 I added a couple of suggestion / questions 😄

[krzysztofzuraw]

@JannikZed please update your branch - it should now have pnpm 9.12.3 :)

[lkostrowski]

@JannikZed let's avoid that, now importing any other APL will evaluate redis, this causes issues, e.g. next is poor at tree shaking, possibly fail because it can't import redis sdk

Please check package.json and add exports key with new path, like vercel-kv. For example

    "./APL/redis": {
      "types": "./APL/redis/index.d.ts",
      "import": "./APL/redis/index.mjs",
      "require": "./APL/redis/index.js"
    },

also new entry point will be needed

https://github.com/saleor/app-sdk/blob/main/tsup.config.ts#L13

[JannikZed]

@IKarbowiak alright, check it out, if that works for you.
Is there a very easy way to test also if the package got build correctly and we can actually use the different APLs? are you spinning up an example saleor app and installing it locally or how are you doing that?

[lkostrowski]

I would do this

1. build sdk
2. set up app-template
3. add sdk locally like pnpm add ../saleor-app-sdk
4. pnpm install
5. try it

of course other APLs must work if redis package is not installed

[lkostrowski]

LGTM

[JannikZed]

@krzysztofzuraw @lkostrowski I added redis integration tests now as well. They don't run automatically, as they need a running redis instance. I think it can help a lot to keep the quality high, as we test if the build is working and the final package can actually work with a real redis. Let me know, what you think. I can quickly remove it again, if that is not what you are expecting.

[lkostrowski]

@JannikZed I'm fine with integration, but it has to be at least in readme how to run it. Best if you prepare docker-compose and document how to run it from scratch (run docker container, then run tests etc)

[JannikZed]

@lkostrowski got it - included that now

[JannikZed]

@andrzejewsky so it is just you remaining :)