Rename app modules to follow convention *.module.ts #472

New Issue

fergalmoran · 2025-08-09T17:16:25Z

fergalmoran commented

2025-08-09 17:16:25 +00:00

Originally created by @kubaszumiato on 8/25/2017

I was struggling to set up AngularCLI to generate components for my Angular app with the newest templates, there is a small trick that I had to do to make it recognize the main app module. I had to rename the app.module.browser.ts to app.browser.module.ts.

Is there any reason for such convention of modules' files naming? Angular team recommendations for naming of modules is with module.ts suffix, could you change this in your templates to follow this recommendation? Would you find such PR reasonable for all 3 modules in app folder of Angular template (browser, server, shared)?

*Originally created by @kubaszumiato on 8/25/2017* I was struggling to set up AngularCLI to generate components for my Angular app with the newest templates, there is a small trick that I had to do to make it recognize the main app module. I had to rename the *app.**module.browser**.ts* to *app.**browser.module**.ts*. Is there any reason for such convention of modules' files naming? Angular team recommendations for naming of modules is with module.ts suffix, could you change this in your templates to follow this recommendation? Would you find such PR reasonable for all 3 modules in app folder of Angular template (browser, server, shared)?

fergalmoran closed this issue

2025-08-09 17:16:25 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#472