-
Notifications
You must be signed in to change notification settings - Fork 5
Closed
Labels
@arkenv/vite-pluginIssues or Pull Requests involving the Vite plugin for ArkEnvIssues or Pull Requests involving the Vite plugin for ArkEnvarkenvChanges to the `arkenv` npm package.Changes to the `arkenv` npm package.bugSomething isn't workingSomething isn't working
Description
ArkType 2.1.28 has introduced a change that actually breaks some of our type work in arkenv, which specifically fails the typecheck of the @arkenv/vite-plugin:
- chore(deps): update dependency arktype to v2.1.28 - autoclosed #490
- https://github.com/yamcodes/arkenv/actions/runs/19973063070/job/57282381954?pr=490
We can solve this by typing EnvSchema better, or, in the interim, use "as any" in the createEnv call within the @arkenv/vite-plugin.
The above is more of a workaround than an idea solution (because any sux) but it solves the issue at hand without creating any issues for consumers. It's just less ideal to work with internally. Do note that even ArkType recommends casting from time to time.
Maybe we can find something better than any or, again, maybe we can find a better type for EnvSchema. (Use Standard Schema directly?)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
@arkenv/vite-pluginIssues or Pull Requests involving the Vite plugin for ArkEnvIssues or Pull Requests involving the Vite plugin for ArkEnvarkenvChanges to the `arkenv` npm package.Changes to the `arkenv` npm package.bugSomething isn't workingSomething isn't working