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
{{ message }}
Repository navigation
io-ts-http unmet peer dependencies of io-ts-types #415
It seems like some peer dependencies of io-ts-types are not met through this package and have to be installed on all clients. Is it possible to add these to the dependencies of io-ts-http?:
➤ YN0002: │ @api-ts/io-ts-http@npm:2.1.0 doesn't provide monocle-ts (p2db90), requested by io-ts-types
➤ YN0002: │ @api-ts/io-ts-http@npm:2.1.0 doesn't provide newtype-ts (p4f369), requested by io-ts-types
My bad should have included the package manager as it is key here. Yarn berry does not automatically install peer dependencies which could lead to this issue
Package manager: Yarn berry
nodejs version: 18
My colleague informed me that this was an explicit decision to place these as peer deps (by io-ts) so the client must install it an ensure every lib in the chain is using the same version. However it would be useful to note this for any other yarn-berry users that it'll not work by default and additional libs must be installed at the application level
Activity
ericcrosson-bitgo commentedon Feb 28, 2023
Hi @arijoon, can you please provide more details on how to reproduce?
With the package.json created by:
package.json
{ "name": "api-ts-issue-415", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "keywords": [], "author": "", "dependencies": { "@api-ts/io-ts-http": "^2.1.0" } }I can run
npm install node -e "const _ = require('@api-ts/io-ts-http')"without error.
Some information that might help: what package manager are you using? What version of Node.js are you using (if any)?
arijoon commentedon Mar 2, 2023
My bad should have included the package manager as it is key here. Yarn berry does not automatically install peer dependencies which could lead to this issue
Package manager: Yarn berry
nodejs version: 18
My colleague informed me that this was an explicit decision to place these as peer deps (by io-ts) so the client must install it an ensure every lib in the chain is using the same version. However it would be useful to note this for any other yarn-berry users that it'll not work by default and additional libs must be installed at the application level