a is not a function about wonka

[shukii]

@kitten any ideas?

[kitten]

Without a reproduction there's not much I can do. Unless you're using Wonka independently though, this is more of a question to post ok the urql repo. On the other hand though, the caveat here is that it must be an issue with the build process or repo itself you may have inadvertently caused here.

However, since the stacktrace here doesn't include call sites, code, and isn't pointing at the correct line even, I can't even guess what's going on 😅

[shukii]

Any luck with this @kitten? We're still facing it a year later and didn't get the answer from the other repo

[kitten]

@shukii Not sure when why this is happening but I'm preparing the repository to move over to TypeScript. urql will move over with the next major bump which will also ditch IE11 support and target ES2015 only.

I've tried this out, and if your environment is set up for it correctly, you should now get full sourcemaps on Wonka. So, potentially, a much easier time debugging.

That said, without a reproduction I can't help you here further myself. This is likely caused by a faulty exchange, faulty usage that shouldn't pass type checks, or an old version/bug that's fixed already 😅

Edit: If you can force a specific version though via Yarn resolutions, or if you simply copy the v6.0.0 source into your node_modules/wonka/ folder, you should already be able to try this out btw