unable to install '@strapi/client' due to tsconfig builder
unable to install '@strapi/client' due to tsconfig compile settings:
KHi @Kofi_anan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
K----------------------
Based on the error message you've provided, it appears you're encountering an issue related to TypeScript configuration settings when trying to use the '@strapi/client' package in your Wasp project. This error suggests that the TypeScript compiler is having trouble resolving the module due to the current 'moduleResolution' setting.
To resolve this issue, you need to update your TypeScript configuration. Specifically, you should change the 'moduleResolution' setting in your tsconfig.json file. Here are the steps you can take:
After making this change, try rebuilding your project.
It's worth noting that Wasp has recently undergone some changes in its TypeScript configuration approach. According to the Github issue about tsconfig story, Wasp 0.12.0 introduced changes to how TypeScript configurations are handled, moving away from separate client and server configurations to a single tsconfig per project.
If you continue to face issues after updating your tsconfig.json, you might want to try the following:
Based on the error message you've provided, it appears you're encountering an issue related to TypeScript configuration settings when trying to use the '@strapi/client' package in your Wasp project. This error suggests that the TypeScript compiler is having trouble resolving the module due to the current 'moduleResolution' setting.
To resolve this issue, you need to update your TypeScript configuration. Specifically, you should change the 'moduleResolution' setting in your tsconfig.json file. Here are the steps you can take:
- Locate your tsconfig.json file in your Wasp project.
- Update the 'moduleResolution' setting to one of the suggested options: 'node16', 'nodenext', or 'bundler'.
After making this change, try rebuilding your project.
It's worth noting that Wasp has recently undergone some changes in its TypeScript configuration approach. According to the Github issue about tsconfig story, Wasp 0.12.0 introduced changes to how TypeScript configurations are handled, moving away from separate client and server configurations to a single tsconfig per project.
If you continue to face issues after updating your tsconfig.json, you might want to try the following:
- Run
to remove all generated files and node_modules.wasp clean - Run
to reinstall everything and regenerate the necessary files.wasp start
KIf the problem persists, you may need to check if you're using the latest version of Wasp, as newer versions might have improvements in handling TypeScript configurations and module resolutions.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
KSorry @Kofi_anan, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Perhaps try again in 15mins?
Kre the bot response, wasp is preventing me from making any tsconfig changes
MLet me try installing 
@strapi/client and see if I can get it to work M@Filip please take a look at this
I've received a consistent error message as user by installing the lib via
I've received a consistent error message as user by installing the lib via
npm install @strapi/client and importing it in either server or client code.