Hi,
In a monorepo that is registered as one project in SonarCloud I have one tsconfig.json that extends another tsconfig in a different package within the monorepo, like this:
That’s weird, we use the same TS you are using to build your project. shared-tsconfigs/js-library.json is it relative to .../package-name/tsconfig.json? Or how does the resolution work in your case?
Well, we run it as a bitbucket pipeline, and I have bitbucket-pipelines.yml in the root directory, and it that I have these steps:
So I assume npm i in the root dir would be enough, as that is how I would install node_modules in all workspaces.
steps:
- step: &build-test-sonarcloud
name: Build, test and analyze on SonarCloud
caches:
- node # See https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html
- sonar
script:
- npm i # Build your project and run
- pipe: sonarsource/sonarcloud-scan:1.4.0