Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature request: add an option to clean outDir on transpilation #20112

Closed
jsamr opened this issue Nov 17, 2017 · 2 comments
Closed

Feature request: add an option to clean outDir on transpilation #20112

jsamr opened this issue Nov 17, 2017 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@jsamr
Copy link

jsamr commented Nov 17, 2017

Scenario: As a user, I would like to clean compilerOptions.outDir before transpiling. It is fairly understandable that it is not the default behavior since removing user data goes beyond the scope of a compiler responsibility. However, many users would find this very convenient during development process, notably:

  • when --watch mode on
  • to systematically avoid "dead leaves", i.e. obsolete sources and definitions

Such a compiler option could be labeled autoCleanOutDir and have boolean type.

Related issues: #13722
@mhegazy
Copy link
Contributor

mhegazy commented Nov 17, 2017

Duplicate of #16057

@mhegazy mhegazy marked this as a duplicate of #16057 Nov 17, 2017
@mhegazy mhegazy added the Duplicate An existing issue was already created label Nov 17, 2017
@jsamr
Copy link
Author

jsamr commented Nov 19, 2017

I close in favor of #16057

@jsamr jsamr closed this as completed Nov 19, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
everhardt referenced this issue in withthegrid/platform-sdk Oct 18, 2019
@everhardt
chore: propagate changeClient
1d3ab89
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Duplicate An existing issue was already created
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jsamr @mhegazy