Ngx-admin: awesome-typescript-loader: TypeError: Cannot convert undefined or null to object

[zeqk]

• I'm submitting a ...
  [*] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository

• What is the current behavior?
  Npm compilation error
  When I run "npm start" in the project (the original project ng2-admin, commit 7215b0b636b2d3ba23560bbeee6745a6677b17d6), or before some change in the code, the result is:

[4] ./~/ionicons/fonts/ionicons.woff?v=2.0.1 83 bytes {0} [built]
            [] -> factory:198ms building:363ms = 561ms
        [5] ./~/css-loader!./~/sass-loader?sourceMap!./src/app/theme/initial.scs
s 66 kB {0} [built]
             factory:3ms building:3972ms = 3975ms
webpack: bundle is now VALID.
webpack: bundle is now INVALID.
DLL: Checking if DLLs are valid.
DLL: All DLLs are valid.
TypeError: Cannot convert undefined or null to object
    at Compiler.<anonymous> (C:\NProjects\ng2-admin\node_modules\awesome-typescr
ipt-loader\src\instance.ts:334:37)
    at next (C:\NProjects\ng2-admin\node_modules\tapable\lib\Tapable.js:140:14)
    at Compiler.Shared.share.compilerInvalid (C:\NProjects\ng2-admin\node_module
s\webpack-dev-middleware\lib\Shared.js:138:5)
    at next (C:\NProjects\ng2-admin\node_modules\tapable\lib\Tapable.js:140:14)
    at Compiler.compiler.plugin (C:\NProjects\ng2-admin\node_modules\webpack\lib
\CachePlugin.js:32:5)
    at next (C:\NProjects\ng2-admin\node_modules\tapable\lib\Tapable.js:140:14)
    at C:\NProjects\ng2-admin\node_modules\src\DllBundlesPlugin.ts:73:20
    at process._tickCallback (internal/process/next_tick.js:103:7)
webpack: wait until bundle finished: /

I can load the site (ex. localhost:3000)

• What is the expected behavior?

No errors compilation

• What is the motivation / use case for changing the behavior?
  The original code of ng2-admin, commit 7215b0b636b2d3ba23560bbeee6745a6677b17d6),
  run:
  npm start

• Please tell us about your environment:
  npm v 3.9.5
  node v 6.2.1
  Windows 8.1 enterprise, 64 bits

[nnixaa]

Hey @zeqk, have you tried the following:

rm -rf node_modules
npm cache clean
npm install
npm start

Let me know if this helps.

[zeqk]

@nnixaa yes! thank you!