arktype•3mo ago

Has anyone been able to get `arktype` working in React Native/Expo?

I found this issue (https://github.com/arktypeio/arktype/issues/1027) but there doesn't seem to be any resolution (no pun intended...). I spent a couple hours trying different configurations but didn't have any luck. Just thought I would check if anyone has found a way to use arktype in a React Native project. Looks like a great library and I'd love to be able to pull it in.

GitHub

Unable to use ArkType with Expo · Issue #1027 · arktypeio/arktype

Report a bug 🔎 Search Terms @babel/plugin-transform-class-static-block expo 🧩 Context ArkType version: 2.0.0-dev.25 TypeScript version (5.1+): 5.5.2 Other context you think may be relevant (JS flav...

30 Replies

ssalbdivad•3mo ago

You can take a look at some additional discussion here: https://discord.com/channels/957797212103016458/1151222272250613802/1151222272250613802 Are you getting the same error that was mentioned in this issue?

bslutherOP•3mo ago

If I just install arktype, the error I get is: Unable to resolve "@ark/schema/config" from "node_modules/arktype/out/config.js".

ssalbdivad•3mo ago

Does it not support package.json exports? That has been around since Node 12 You could try manually replacing that import with the primary @ark/schema entrypoint to see what happens

bslutherOP•3mo ago

Ok I'll give that a shot. There is also a metro setting that I tried, turning it on looks like this

// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require('expo/metro-config')

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname)
config.resolver.unstable_enablePackageExports = true

module.exports = config

// Learn more https://docs.expo.io/guides/customizing-metro
const { getDefaultConfig } = require('expo/metro-config')

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname)
config.resolver.unstable_enablePackageExports = true

module.exports = config

Which gets me to a new error message, import.meta is currently unsupported. There's a Babel plugin I tried, babel-plugin-transform-import-meta, can't remember what the error was with that but couldn't get it to work either. I'm just importing type, eg import { type } from 'arktype' so it's happening under the hood somewhere

ssalbdivad•3mo ago

It seems like a lot of ESM features aren't supported Also are you using the latest version of arktype? I think based on our last conversation I wrapped import.meta in a try catch, unless that doesn't help because it's some static analysis process that doesn't are?

bslutherOP•3mo ago

I just installed so I assume so, "^2.0.4"

ssalbdivad•3mo ago

Sorry I'm so unfamiliar with the ecosystem, but I assume if they want modern packages to be usable, they must have some recommendation of how you're supposed to transpile modern JS? I'm not using anything that doesn't have broad support in ESM at this point, so it feels like there should be some recommended transpiler option for modern js => whatever they need

ssalbdivad•3mo ago

Yeah so I guess if it's static hermes it's trying to analyze it even though it's wrapped in a try catch 🫠

bslutherOP•3mo ago

Yea it seems crazy, every time I have problems like this with react native I wonder why it's a problem.. I'm going to try stepping through the whole process again, I will post here for posterity. So using babel-plugin-transform-import-meta had no effect, same error. I wonder if this has to do with using pnpm, I know there are some issues with monorepos and react native. I might try switching to yarn and seeing if the problem persists. Interesting, I changed from node 18 to node 22 and I get a new error now, intersection.equals is not a function (it is undefined)

ssalbdivad•3mo ago

I mean ArkType is doing a lot of binding for and tricks for JIT optimizations. Obviously it's all a stable part of JS but maybe if hermes is trying to statically analyze it it can't?

bslutherOP•3mo ago

Seems weird, but who knows. Hoping maybe someone else out there has used arktype with react native and could share some insight I tried yarn and that didn't help

ssalbdivad•3mo ago

Yeah I'm sure over time things will be fleshed out on one or both sides. From what I've heard static hermes is still pretty early-days in terms of stability. I'd assume the goal is to be able to support the same modern JS that gets shipped for other runtimes

bslutherOP•3mo ago

Yea, I certainly hope so

bslutherOP•2mo ago

@ssalbdivad Just wanted to mention that I got it working thanks to the change mentioned in this issue: https://github.com/arktypeio/arktype/issues/1027#issuecomment-2656650793. I posted a reply there with the steps that got it working for me if anyone else runs into this.

GitHub

Unable to use ArkType with Expo · Issue #1027 · arktypeio/arktype

ssalbdivad•2mo ago

Sweet! Will definitely take a look at this so hopefully I have somewhere to point people struggling with React Native in the future

bslutherOP•2mo ago

Many thanks to mark-lendit for figuring that out 👏

Tobias•2mo ago

I have very similiar issues even with the fix, unfortunately I can't enable unstable_enablePackageExports because that breaks the whole app (SurfaceRegistryBinding::startSurface failed. Global was not installed.) I am really clueless When changing this, I get the import.meta issue The babel plugin doesn't help with import meta. for me Also monorepo (ofc) back to stone age! (zod) This was on Arktype 2.1.6

bslutherOP•2mo ago

Did you try the other things I mentioned on the issue? That's all I know to suggest really. Had to specify es6 for the babel plugin, ["babel-plugin-transform-import-meta", { "module": "ES6" }]

Tobias•2mo ago

Yeah, I did that

bslutherOP•2mo ago

Ah ok, dang. Are you using pnpm?

Tobias•2mo ago

yes

bslutherOP•2mo ago

The pnpm/monorepo setup seems like it can throw a wrench in with react native, I wonder if it's related.

Tobias•2mo ago

I assume it might be to what happens when I enable unstable_enablePackageExports It's such a bummer React Native is so broken when it comes to package handling

bslutherOP•2mo ago

I know, every other week I think about capacitor. Don't know if its actually any better

Tobias•2mo ago

I assume it will be solved eventually. Symlink support was also added last year...

bslutherOP•2mo ago

The only other things I might suggest is clearing your pnpm cache, metro cache, deleting node_modules and anything else you can think of

Tobias•2mo ago

yeah, already tried all of that

bslutherOP•2mo ago

Dang, ok, sorry Changing node version too? I'm still at a loss of why that mattered. But that was the last thing I did and it started working after. I wonder if it just forced my yarn cache to rebuild

Tobias•2mo ago

hm nope I will try again in the future Maybe after the next torture of updating Expo SDK and react 19

bslutherOP•2mo ago

I was on node 18 and switched to 22. Now it runs fine on 18 again so, that's why I think maybe it was the change not the version itself

Gaming

Programming

Has anyone been able to get `arktype` working in React Native/Expo?

Did you find this page helpful?