Skip to content

Please add a flag to suppress the warning, Add only entry points to the 'files' or 'include' properties in your tsconfig. #30013

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.

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

Closed
wcwcaseman opened this issue Apr 2, 2025 · 3 comments

Comments

@wcwcaseman
Copy link

Which @angular/* package(s) are relevant/related to the feature request?

No response

Description

In my NX Angular project I add entry points in webpack. Depending on some conditions I add certain env.ts files to the project. I have hundreds of different env.x.ts files for our many different environments. So depending on the chosen build many of these env.ts files won't be entry points for the application. However to compile these I need to set "include": ["/*.d.ts", "/env**.ts"] in tsconfig.app.json . This means the env.x.ts files I will be using get compiled but the ones i'm not using are output as warnings.

Proposed solution

Add a flag that can be set to turn off the following warning , "Add only entry points to the 'files' or 'include' properties in your tsconfig."

Alternatives considered

no alternatives to consider.

@alan-agius4
Copy link
Collaborator

This is not longer an issue with the application builder.

No new features are added to the webpack based builders.

@alan-agius4 alan-agius4 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2025
@wcwcaseman
Copy link
Author

@alan-agius4 Are you saying this warning won't show up in Angular 19? , I am on version 18.2.9.

Or are you saying you won't fix it because i'm using webpack?

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants