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
Suddenly I found out that yarn does NOT respect yarn.lock files of sub-dependencies. So the version of zod defined in my yarn.lock file does not actually mean anything when doing yarn add express-zod-api.
When you publish a package that contains a yarn.lock, any user of that library will not be affected by it. When you install dependencies in your application or library, only your own yarn.lock file is respected. Lockfiles within your dependencies will be ignored.
Holy Moly!
The version of Zod 3.10.x seems to have some breaking changes and it should not be installed according to my lock file included to the package distribution, but yarn installs this version along with my library and it causes the following error.
Suddenly I found out that
yarn
does NOT respectyarn.lock
files of sub-dependencies. So the version ofzod
defined in myyarn.lock
file does not actually mean anything when doingyarn add express-zod-api
.Related issue: yarnpkg/yarn#4928
https://classic.yarnpkg.com/blog/2016/11/24/lockfiles-for-all/
Holy Moly!
The version of Zod 3.10.x seems to have some breaking changes and it should not be installed according to my lock file included to the package distribution, but yarn installs this version along with my library and it causes the following error.
The text was updated successfully, but these errors were encountered: