Is there an existing issue for this?
Current behavior
As discussed in #3454 and #3460, the hard cap protecting the use of both configs in the outside directory was a regression as there are valid use cases for outputting build artifacts outside the package boundary, and some existing workflows depend on this behavior.
Minimum reproduction code
outDir": "../nest-cli-delete-outside",
Steps to reproduce
No response
Expected behavior
We'll expose them under a flag in v11, and can keep it disabled as default to avoid breaking changes.
To be changed in v12
Package version
11.0.22
NestJS version
No response
Node.js version
No response
In which operating systems have you tested?
Other
No response
Is there an existing issue for this?
Current behavior
As discussed in #3454 and #3460, the hard cap protecting the use of both configs in the outside directory was a regression as there are valid use cases for outputting build artifacts outside the package boundary, and some existing workflows depend on this behavior.
Minimum reproduction code
outDir": "../nest-cli-delete-outside",
Steps to reproduce
No response
Expected behavior
We'll expose them under a flag in v11, and can keep it disabled as default to avoid breaking changes.
To be changed in v12
Package version
11.0.22
NestJS version
No response
Node.js version
No response
In which operating systems have you tested?
Other
No response