Skip to content

Commit 49e72a9

Browse files
devversionjelbourn
authored andcommitted
build: ensure to never output files next to sources (#17362)
We have a few tsconfig files which are not used by Bazel and therefore can be run manually/or by IDEs. In any case, for these TS projects we never want to output the JS files next to the sources. This would cause the files to show up in the Git repository tree. The scenario that someone runs this manually, or that IDEs build the project somehow is rare, but it's generally good setting the output directory for these tsconfig files. Note: we cannot do this for the Bazel tsconfig files as this would result in warnings from `@bazel/typescript`
1 parent b836050 commit 49e72a9

File tree

3 files changed

+3
-0
lines changed

3 files changed

+3
-0
lines changed

scripts/tsconfig.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"compilerOptions": {
3+
"outDir": "../dist/dev-infra-scripts",
34
"lib": ["es2016"],
45
"types": ["node"],
56
"strictNullChecks": true

tools/cherry-pick-patch/tsconfig.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"compilerOptions": {
3+
"outDir": "../../dist/tools/cherry-pick-patch",
34
"lib": ["es2016"],
45
"types": ["node"],
56
"strictNullChecks": true

tools/release/tsconfig.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"compilerOptions": {
3+
"outDir": "../../dist/tools/release",
34
"lib": ["es2016"],
45
"types": ["node"],
56
"strictNullChecks": true

0 commit comments

Comments
 (0)