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
This is the behavior in every version I tried, and I reviewed the FAQ for entries about build, outDir, incremental
I was unable to test this on prior versions because _______
⏯ Playground Link
N/A
💻 Code
N/A
🙁 Actual behavior
Error reported instead of generating compiled files in the specified directory.
error TS5072: Unknown build option '--outDir'.
🙂 Expected behavior
Expect compiled files generated in the specified directory. This is required for CI pipelines to work without having to modify the source, so build output is generated in the build directory for the current pipeline run and not in the source directory, as it is done in development.
I also will add that the docs are written like a novel not as a technical documentation and it's very hard to navigate them. For this specific issue, it should list which options --build can be combined with and which won't work with it. If somehow, in some unimaginable way, this turns out to be behavior by design, you should update the docs saying that --build generates incremental builds only in the project's outDir and cannot be changed via CLI options.
The text was updated successfully, but these errors were encountered:
Bug Report
If
tsc
is executed with--build
, supplying--outDir
fails:The error is reported as:
error TS5072: Unknown build option '--outDir'.
🔎 Search Terms
"--outDir" "--build"
🕗 Version & Regression Information
tsc v4.2.2
⏯ Playground Link
N/A
💻 Code
N/A
🙁 Actual behavior
Error reported instead of generating compiled files in the specified directory.
error TS5072: Unknown build option '--outDir'.
🙂 Expected behavior
Expect compiled files generated in the specified directory. This is required for CI pipelines to work without having to modify the source, so build output is generated in the build directory for the current pipeline run and not in the source directory, as it is done in development.
I also will add that the docs are written like a novel not as a technical documentation and it's very hard to navigate them. For this specific issue, it should list which options
--build
can be combined with and which won't work with it. If somehow, in some unimaginable way, this turns out to be behavior by design, you should update the docs saying that--build
generates incremental builds only in the project'soutDir
and cannot be changed via CLI options.The text was updated successfully, but these errors were encountered: