There are multiple modules with names that only differ in casing.

Please provide us with the following information:

OS?

Windows 10 [MINGW64 -> git-bash for windows]

Versions.

$ ng -v
    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/
@angular/cli: 1.0.0-rc.0
node: 6.10.0
os: win32 x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
@angular/cli: 1.0.0-rc.0
@angular/compiler-cli: 2.4.8

Repro steps.

app.component.ts

@Component({
  selector: 'app',
  styleUrls: [
    './app.component.css'
  ],
  template: `
	...
  `
})
export class AppComponent implements OnInit { ... }

warning

$ cnpm start

> ng2-proj@0.0.0 start H:\a0a\ws\ng2-da
> ng serve

** NG Live Development Server is running on http://localhost:4200 **
Hash: 6f8d77c1639eead950f6
Time: 22080ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 153 kB {3} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 58.2 kB {3} [initial] [rendered]
chunk    {2} main.bundle.js, main.bundle.js.map (main) 3 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

WARNING in ../ng2-proj/~/.0.26.2@css-loader/lib/css-base.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
* H:\a0a\ws\ng2-proj\node_modules\.0.1.6@source-map-loader\index.js!H:\a0a\ws\ng2-proj\node_modules\.0.26.2@css-loader\lib\css-base.js
    Used by 2 module(s), i. e.
    H:\a0a\ws\ng2-proj\node_modules\.0.26.2@css-loader\index.js?{"sourceMap":false,"importLoaders":1}!H:\a0a\ws\ng2-proj\node_modules\.0.13.0@postcss-loader\index.js!H:\a0a\ws\ng2-da\src\styles\common.css
* H:\a0a\ws\ng2-proj\node_modules\.0.1.6@source-map-loader\index.js!h:\a0a\ws\ng2-proj\node_modules\.0.26.2@css-loader\lib\css-base.js
    Used by 1 module(s), i. e.
    H:\a0a\ws\ng2-proj\node_modules\.0.6.4@exports-loader\index.js?module.exports.toString()!H:\a0a\ws\ng2-proj\node_modules\.0.26.2@css-loader\index.js?{"sourceMap":false,"importLoaders":1}!H:\a0a\ws\ng2-proj\node_modules\.0.13.0@postcss-loader\index.js!h:\a0a\ws\ng2-da\src\app05\app.component.css
webpack: Compiled with warnings.

---

app.component.ts

@Component({
  selector: 'app',
  template: `
	...
  `
})
export class AppComponent implements OnInit { ... }

success

$ cnpm start

> ng2-proj@0.0.0 start H:\a0a\ws\ng2-da
> ng serve

** NG Live Development Server is running on http://localhost:4200 **
Hash: dd34e8f8e812d41aac01
Time: 21175ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 153 kB {3} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 58.2 kB {3} [initial] [rendered]
chunk    {2} main.bundle.js, main.bundle.js.map (main) 3 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
webpack: Compiled successfully.

The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

---

Thanks! We’ll be in touch soon.

[gangadharjannu]

I got this issue when I mistakenly imported ‘Router’ instead of router. So I’ve used
import { Router } from '@angular/Router'; instead of
import { Router } from '@angular/router'; (Correct one)

[Brocco]

I have researched this a bit and it appears that the drive letter you’re using may the cause… more specifically the case of the drive letter you’re using.

If you are currently use c:\path-to-project try changing it to C:\path-to-project

This has been reported by multiple people on multiple build tools it does not appear to be an issue with the CLI itself, therefore closing this issue.