Standard Schema Resolver `Could not resolve "@standard-schema/utils"`

[ryanagillie]

Describe the bug
Standard schema resolver fails to import @standard-schema/utils

To Reproduce

1. Go to https://stackblitz.com/edit/vitejs-vite-neec4edf?file=src%2FApp.tsx
2. Check console
3. See error

Expected behavior
Have the standard schema resolver not have an import error on @standard-schema/utils

Screenshots

[ryanagillie]

Gonna cc @EskiMojo14 as this started happening with the most recent fix for the resolver

[EskiMojo14]

ah - probably need to move it from devDeps to normal deps
I'm out but can file a PR later if nobody gets there first

[EskiMojo14]

okay, so the difference with the standard-schema resolver vs the individual library resolvers is that the user likely won't already have @standard-schema/spec and @standard-schema/utils installed.

Possible solutions:

• make sure all users have them installed by including them as explicit dependencies
  • this means they get installed for everyone, including people who won't use standardSchemaResolver (bigger node_modules, but shouldn't be in build)
• document somewhere that standardSchemaResolver users also need to install them manually
  • if doing this, they should still probably be optional peer dependencies to ensure compatible versions.

[EskiMojo14]

once installed, reproduction builds successfully: https://stackblitz.com/edit/vitejs-vite-es3gsqwe?file=package.json

[github-actions]

🎉 This issue has been resolved in version 4.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[graup]

make sure all users have them installed by including them as explicit dependencies
this means they get installed for everyone, including people who won't use standardSchemaResolver

I think this is a pretty ugly solution. Is there no better way?

[EskiMojo14]

I think this is a pretty ugly solution. Is there no better way?

Making it an optional peer dependency, which is also pretty ugly.

to be frank, the end goal of Standard Schema is that the concept of a "resolver" is no longer necessary, since all compliant libraries speak the same language.

I don't know if there are specific benefits at the moment to using a specific resolver for your schema library of choice (and I'm sure there are some supported that don't currently support Standard Schema), but eventually™ RHF should be able to remove the need for a resolver, and everybody uses standard schema.

you can see this in libraries like next-safe-action, who have been able to simplify their code massively by removing adapters and only supporting standard schema.

[graup]

Thanks for the context. I thought Standard Schema is just another validation library, but if it's a standard API going to used everywhere, I guess it makes sense to have that as a general dependency!

[EskiMojo14]

yep! check out https://standardschema.dev/ for more info :)