Angular RC5 app updated from CLI beta 10 to webpack 2 giving issues.

1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) El Capitan
2. Versions. Please run ng --version. If there’s nothing outputted, please run in a Terminal: node --version and paste the result here: angular-cli: 1.0.0-beta.11-webpack.2 node: 4.4.7 os: darwin x64
3. Repro steps. Was this an app that wasn’t created using the CLI? What change did you do on your code? etc. The app was created using angular-cli.beta.10 and now trying to upgrade it to 11-webpack-2

The app compiles just fine without any issues.

However the http://localhost:4200 just shows loading.... text.

In Browser console it spits out:

url_resolver.js:238 Uncaught TypeError: uri.match is not a function_split @ url_resolver.js:238 getUrlScheme @ url_resolver.js:80 componentModuleUrl @ metadata_resolver.js:750 CompileMetadataResolver.getDirectiveMetadata @ metadata_resolver.js:155(anonymous function) @ metadata_resolver.js:267 CompileMetadataResolver.getNgModuleMetadata @ metadata_resolver.js:260(anonymous function) @ metadata_resolver.js:252 CompileMetadataResolver.getNgModuleMetadata @ metadata_resolver.js:239 RuntimeCompiler._compileComponents @ runtime_compiler.js:150 RuntimeCompiler._compileModuleAndComponents @ runtime_compiler.js:72 RuntimeCompiler.compileModuleAsync @ runtime_compiler.js:49 PlatformRef_._bootstrapModuleWithZone @ application_ref.js:368 PlatformRef_.bootstrapModule @ application_ref.js:361(anonymous function) @ main.ts:9__webpack_require__ @ bootstrap 7dca594…:52(anonymous function) @ environment.dev.ts:6__webpack_require__ @ bootstrap 7dca594…:52webpackJsonpCallback @ bootstrap 7dca594…:23(anonymous function) @ main.bundle.js:1

Am not fully sure where or how to start debugging this issue. Please kindly help me.

P.S: It was a working app before the update to webpack version.

[vapits]

Remove module.id from all components. This will solve your issues.

[angular-automatic-lock-bot[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.}