Import statements now case sensitive but in production / aot only

[slubowsky]

Upgraded to version 6. Production builds began failing. Eventually figured out cause was apparently newly introduced case sensitivity of import statements.

Versions

Angular CLI: 6.0.0
Node: 9.11.1
OS: win32 x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

• Use different case in directory names and / or file names then is used in import statement
  e.g directory is named

some-Form

import statement uses

some-form

• ng serve --prod

Observed behavior

ERROR in : Cannot determine the module for class SomeFormComponent in D:/dev/my-app-clone2/src/app/my/shared-inputs/some-Form/some-form.component.ts! Add SomeFormComponent to the NgModule to fix it.

Desired behavior

• Same behavior regardless of prod/aot or not
• At least a more useful error message

Mention any other details that might be useful (optional)

[Hypenate]

I had the same issue with a path, I had the path:

user-management/clear-Password/clear-password.component

In my NgModule I referenced to:

user-management/clear-password/clear-password.component

A change the path from clear-Password to clear-password and the error disappeared.

[filipesilva]

Case sensitive imports are generally a characteristic of the underlying OS, not of the build system itself. You should always use the correct path with the correct case.

That being said I agree it is odd if it works in dev but not in prod. I think it should not work in either one. Just tried it myself and can confirm it breaks in prod but not in dev.

[alan-agius4]

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.

If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

[angular-automatic-lock-bot]

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.}