You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned here, the play script is currently not functional in the v2 branch. The error below occurs.
$ yarn play
yarn run v1.22.5
$ nodemon -e ts -w . -x ts-node src/playground.ts --project tsconfig.json
[nodemon] 2.0.2
[nodemon] to restart at any time, enter `rs`
[nodemon] watching dir(s): *.*
[nodemon] watching extensions: ts
[nodemon] starting `ts-node src/playground.ts --project tsconfig.json`
sh: ts-node: command not found
[nodemon] failed to start process, "ts-node" exec not found
[nodemon] Error
at Bus.<anonymous> (./zod/node_modules/nodemon/lib/nodemon.js:156:25)
at Bus.emit (events.js:327:22)
at ChildProcess.<anonymous> (./zod/node_modules/nodemon/lib/monitor/run.js:167:11)
at ChildProcess.emit (events.js:315:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
✨ Done in 0.32s.
To resolve this, simply adding ts-node to the dev dependencies should be enough. Though, playground.ts also appears to not be in a stable state either. The error below occurs.
Error: You can't call .parse on a schema containing async transformations.
Perhaps also putting playground in a stable state as well may be good for new developers coming in and being able to test out the library right away. A decision here should probably be made on whether this ticket should encompass both issues before a PR is sent in, though 🙂
The text was updated successfully, but these errors were encountered:
As mentioned here, the
play
script is currently not functional in thev2
branch. The error below occurs.To resolve this, simply adding
ts-node
to the dev dependencies should be enough. Though,playground.ts
also appears to not be in a stable state either. The error below occurs.Perhaps also putting playground in a stable state as well may be good for new developers coming in and being able to test out the library right away. A decision here should probably be made on whether this ticket should encompass both issues before a PR is sent in, though 🙂
The text was updated successfully, but these errors were encountered: