Troubleshooting Compose SDK Setup Issues
Troubleshooting Compose SDK Setup Issues
Below are some issues you may run into when setting up a TypeScript+React app to use Compose SDK packages and how you may troubleshoot them. Most of them are related to the app configurations as opposed to SDK-known issues, which are listed here.
If your issue is not on the list or the solution/workaround does not work for you, please leave a comment below. We will verify and update the list accordingly.
# Action Error Message/Behavior Solution/Workaround
|
1 |
yarn install |
RequestError: unable to get local issuer certificate |
Turn OFF Internet Security in Zscaler |
|
2 |
yarn install |
Invalid authentication (as an anonymous user) |
Follow https://gitlab.sisense.com/SisenseTeam/compose-sdk-monorepo/-/blob/master/quickstart-public.md#installing-the-sdk-packages to configure personal access token for GitLab Packages Registry. Also, try deleting yarn.lock and running yarn cache clean --all before running yarn install again |
|
3 |
yarn install |
No @sisense/sdk* modules installed in node_modules Consequently, the CLI command fails to generate the data model without |
Check if Yarn Plug'n'Play is enabled. One sign is the creation of pnp.cjs in the root folder after yarn install. To fix, add nodeLinker: node-modules to .yarnrc.yml in the root folder and run yarn install again. |
|
4 |
CLI command using npx |
No output in the console and the data model file is not generated |
This is also related to Yarn Plug’n’Play being enabled. This feature is available in Yarn 4.x, which is not a stable version. To fix:
|
|
5 |
CLI command |
Error connecting to [Sisense URL] TypeError: fetch failed |
Turn OFF Internet Security in zscaler |
