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
Yeah, the hapi types require the Joi typings to compile. This is not ideal, but how it is currently. I'm sure a PR that decouples it would be very welcome.
You should be able to fix it by installing the joi module as a development dependency.
Are you sure it's not activated by skipLibCheck = false?
If joi is required its not a dev dependency, looking in you packet.json its listed as a dev dependency.
adding it to the project using npm install joi removes the error but this is a hack as i see it.
Joi is only required for compiling the typescript types, so it won't be added as a normal dependency. This is similar to the typescript dev dependency.
This is indeed a hack, because there is no decent solution until someone takes the time to decouple it in the hapi typings. Again a PR would be welcome.
Activity
kanongil commentedon Mar 18, 2024
Yeah, the hapi types require the
Joitypings to compile. This is not ideal, but how it is currently. I'm sure a PR that decouples it would be very welcome.You should be able to fix it by installing the
joimodule as a development dependency.Are you sure it's not activated by
skipLibCheck = false?JimmyBjorklund commentedon Mar 19, 2024
If joi is required its not a dev dependency, looking in you packet.json its listed as a dev dependency.
adding it to the project using npm install joi removes the error but this is a hack as i see it.
kanongil commentedon Mar 19, 2024
Joi is only required for compiling the typescript types, so it won't be added as a normal dependency. This is similar to the
typescriptdev dependency.This is indeed a hack, because there is no decent solution until someone takes the time to decouple it in the hapi typings. Again a PR would be welcome.