Cannot find module './models/config'

Question

Updating my Angular 2 CLI project from 1.0.0-beta.11-webpack.2 to 1.0.0-beta.11-webpack.8 according to instructions:

npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@webpack

resulted in this:

jan@linux-zd16:~/src/fm-repos/fm-ui> ng --version
Cannot find module './models/config'
Error: Cannot find module './models/config'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/jan/src/fm-repos/fm-ui/node_modules/angular-cli/addon/ng2/index.js:4:16)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)

score 4 · Accepted Answer · edited Jan 13 '17 at 16:55

4

When installing Angular CLI, explicitly use the latest version, instead:

Update global Angular CLI

rm -rf node_modules dist tmp
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest

Update project's Angular CLI

npm install --save-dev angular-cli@latest

Update project's configuration files

ng init

and carefully review each difference.

edited Jan 13 '17 at 16:55

István

5,057
10
38
67

answered Sep 14 '16 at 20:19

Jan Nielsen

10,892
14
65
119

I am having the same issue as you, but only get it to work with webpack.8 as well. Were you able to upgrade to beta 15? – cport1 Sep 21 '16 at 18:26
1

yes, @cport1 -- I successfully upgraded to `beta.15`. – Jan Nielsen Sep 21 '16 at 18:28
What did you have to do to get it to work with beta.15? – cport1 Sep 21 '16 at 18:30
1

@cport1 - see my answer at http://stackoverflow.com/questions/39600939/invalid-configuration-object-webpack-has-been-initialised-using-a-configuration. – Jan Nielsen Sep 21 '16 at 18:33

score 2 · Answer 2 · answered Sep 19 '16 at 05:30

Angular 2 has very recently changed it's build engine from SystemJS to Webpack in it's latest release. Which could be one (amongst other) reasons for this error message (it was for me anyway).

If you want to ensure you use the latest, like discussed on their git page, you can run:

npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest //in theory, npm install -g angular-cli should be OK

Now your project is likely still 'setup' to use the previous build system, so it's easier to delete your node_modules, and reinstall:

rm -rf node_modules
npm install

You can verify the installation via:

ng build

Cannot find module './models/config'

2 Answers2

Update global Angular CLI

Update project's Angular CLI

Update project's configuration files

Linked