Is the normalized cache supported when using Kotlin JS

Question

bod · Answer

I m afraid not <https github com apollographql apollo kotlin multiplatform|Here> s the matrix of Multiplatform

John O&apos;Reilly · Answer

ok thanks

John O&apos;Reilly · Answer

I was looking to use in <https github com joreilly PeopleInSpace> which has Kotlin JS client but can factor out use of normalized cache for that platform have done something similar for another library

bod · Answer

we have <https github com apollographql apollo kotlin issues 3442|this issue> open for this we think it may not be too hard but that s often a dangerous statement sweat smile since SQLDelight supports JS

John O&apos;Reilly · Answer

actually that matrix shows that `apollo normalized cache` is available for JS

John O&apos;Reilly · Answer

this is the in memory one I presume

bod · Answer

woops sorry yes that s correct

John O&apos;Reilly · Answer

cool can configure hopefully to use just that then for JS

John O&apos;Reilly · Answer

Getting following for some reason when building Kotlin JS after adding apollo dependencies I ll keep digging but just in case it s something you ve come across ```java lang IllegalStateException FATAL ERROR Could not find io ktor ktor http cio in Users joreilly Library Application Support kotlin daemon at org jetbrains kotlin ir backend js KlibKt$toResolverLogger$1 fatal klib kt 117 at org jetbrains kotlin library KotlinLibrarySearchPathResolver resolve SearchPathResolver kt 175 ```

John O&apos;Reilly · Answer

This is code that still has ktor dependencies perhaps running in to some conflicts between versions used

John O&apos;Reilly · Answer

probably an usual situation to have a project use both apollo and ktor directly had thought I d show both implementation side by side for comparison but might just create separate branch that use apollo

bod · Answer

wave Hey did you manage to resolve it in the end

John O&apos;Reilly · Answer

I ended up keeping this in separate branch without ktor stuff for now I m using Ktor 2 x atm in that project which I think is probably incomaptible

bod · Answer

oh indeed that must be it Apollo is using 1 6 4

John O&apos;Reilly · Answer

I had to move to 2 x in that project to get combination of dependencies that worked on M1 devices and also supported new k n memory model

bod · Answer

Yeah I can imagine It would be nice for Apollo to depend on the more recent one too wondering if that would be a big change I m supposing not too big On the other hand this could break people who want to do this too but are still on Ktor 1 x smile

John O&apos;Reilly · Answer

2 0 is still in beta right now I guess maybe more a potential requirement once it hits stable

John O&apos;Reilly · Answer

have you guys been looking much yet at using new memory model

bod · Answer

Good point

bod · Answer

Re memory model we haven t looked at it too much but it s on the roadmap But yeah I guess waiting for things to be more stable overall slightly smiling face

clark · Answer

Is it still the case that 2 x would be needed to use the new k n memory model

bod · Answer

Not sure about Ktor but Apollo still doesn t support the new memory model at this point