ERROR in Cannot read property 'getSourceFile' of undefined #5329

milenkovic · 2017-03-09T10:48:54Z

Hi, I am trying to configure webpack in order to work with AOT, however I am getting this error. I tried with changing versions but without success, in some cases I even got more errors.

OS?

Windows 10

Versions.

Node: v7.6.0
@ngtools/webpack: 1.2.12

Repro steps.

https://github.com/milenkovic/webpack-angular-aot
npm install
npm run project-aot

The log given by the failure.

ERROR in Cannot read property 'getSourceFile' of undefined

ERROR in C:/Workspace/webpack-aot/public/javascripts/core/projects/main.aot.ts (3,34): Cannot find module './ngfactory/public/javascripts/core/projects/app.module.ngfactory'.)

ERROR in ./public/javascripts/core/projects/main.aot.ts
Module not found: Error: Can't resolve './ngfactory/public/javascripts/core/projects/app.module.ngfactory' in 'C:\Workspace\webpack-aot\public\javascripts\core\projects'
@ ./public/javascripts/core/projects/main.aot.ts 3:0-103

Dobryvechir · 2017-03-11T20:24:35Z

The error lies in node_modules@ngtools\webpack\src\compiler_host.js in function _resolve(path), when the operating system is Windows.
In some cases, this function calls to path.join, which returns a normalized path under the current OS, which does not correspond to the idea of _resolve function to replace backslashes with normal slashes.
Until a new version with this fix appears, you can replace manually that function with the code as follows:
_resolve(path) {
path = this._normalizePath(path);
if (path[0] == '.') {
return this._normalizePath(path_1.join(this.getCurrentDirectory(), path));
}
else if (path[0] == '/' || path.match(/^\w://)) {
return path;
}
else {
return this._normalizePath(path_1.join(this._basePath, path));
}
}
After this, the problem disappears.

PaybackMan · 2017-03-16T20:42:35Z

horrible error message

maffelbaffel · 2017-03-22T12:45:00Z

This error literally cost me 5 hours debugging. Replacing with

_resolve(path) {
        path = this._normalizePath(path);
        if (path[0] == '.') {
            return this._normalizePath(path_1.join(this.getCurrentDirectory(), path));
        }
        else if (path[0] == '/' || path.match(/^\w:\//)) {
            return path;
        }
        else {
            return this._normalizePath(path_1.join(this._basePath, path));
        }
    }

solved it for me thought.

@Dobryvechir's code was missing a backslash:

        else if (path[0] == '/' || path.match(/^\w://)) {
                                                     ^
SyntaxError: Unexpected token )

arlindonatal · 2017-03-22T23:55:43Z

I have the same problem. After changing this method, the error persists:

ERROR in Cannot read property 'getSourceFile' of undefined


ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/utils/hmac-http-client.ts (39,63): Cannot find name 'CryptoJS'.)
/home/arlindo/git/vendedoronline/frontend/src/app/utils/hmac-http-client.ts (41,63): Cannot find name 'CryptoJS'.)
/home/arlindo/git/vendedoronline/frontend/src/app/utils/hmac-http-client.ts (43,63): Cannot find name 'CryptoJS'.)

ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/security/securityToken.ts (5,9): Cannot find name '_'.)

ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/account/account.ts (12,13): Cannot find name '_'.)

ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/empresa/empresa.ts (11,13): Cannot find name '_'.)

ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/fabricante/fabricante.ts (10,13): Cannot find name '_'.)

ERROR in /home/arlindo/git/vendedoronline/frontend/src/app/linha/linha.ts (10,13): Cannot find name '_'.)

The references:

///<reference path="../../../typings/cryptojs/cryptojs.d.ts" />
///<reference path="../../../typings/lodash/lodash.d.ts" />

colltoaction · 2017-03-25T00:34:06Z

I'm on Windows 10 using @ngtools/webpack:1.3.0. I can confirm @maffelbaffel's fix works.

You can paste this into your webpack.config.js and avoid touching the node_modules folder, especially useful for automated deployment scenarios:

// workaround https://github.com/angular/angular-cli/issues/5329
var aotPlugin = new ngToolsWebpack.AotPlugin({
    tsConfigPath: "./tsconfig.aot.json",
    entryModule: path.resolve(__dirname, "./ClientApp/components/main.module#MainModule"),
});
aotPlugin._compilerHost._resolve = function(path_to_resolve) {
    path_1 = require("path");
    path_to_resolve = aotPlugin._compilerHost._normalizePath(path_to_resolve);
    if (path_to_resolve[0] == '.') {
        return aotPlugin._compilerHost._normalizePath(path_1.join(aotPlugin._compilerHost.getCurrentDirectory(), path_to_resolve));
    }
    else if (path_to_resolve[0] == '/' || path_to_resolve.match(/^\w:\//)) {
        return path_to_resolve;
    }
    else {
        return aotPlugin._compilerHost._normalizePath(path_1.join(aotPlugin._compilerHost._basePath, path_to_resolve));
    }
};

DanWahlin · 2017-03-26T17:04:30Z

Thanks for sharing @tinchou! That fixed it for me. Was having the same problem on Windows 10....wasted more time than I care to admit on this issue. :-)

colltoaction · 2017-03-26T18:51:58Z

Yeah, that sucks. The problem is not knowing which one is the broken component after a big update. I was lucky I was glancing over that repo's issues a couple of hours before updating myself.

tavelli · 2017-04-12T20:44:22Z

@tinchou can you share plugins context of your webpack config for this workaround?

colltoaction · 2017-04-13T00:49:02Z

What do you mean? This?

    plugins: [
        aotPlugin,
        new webpack.optimize.UglifyJsPlugin({
            mangle: { screw_ie8: true },
            compress: {
                screw_ie8: true,
                warnings: false,
            }
        }),
        new webpack.LoaderOptionsPlugin({
            minimize: true,
            debug: false
        }),
    // ....

tavelli · 2017-04-13T17:36:32Z

@tinchou yea thanks, i had dumb mistake with var aotPlugin = new ngToolsWebpack.AotPlugin({ part defined after webpack config instead of before

hheexx · 2017-04-13T19:48:53Z

@tinchou screw_ie8: true, is default. You don't need that.

bkdotcom · 2017-04-14T19:29:21Z

where is this webpack.config.js file everyone speaks of along with the aotPlugin settings?
Does @angular/cli use it?
I've been trying to get a --prod and/or --aot build to work for months... seem to be in upgrade/dependency hell / along with not having any idea where the error lines

ng build --aot

No NgModule metadata found for 'AppModule'

expanding that:

ZoneAwareError http://localhost:4200/polyfills.bundle.js:7954:21
NgModuleResolver.prototype.resolve http://localhost:4200/vendor.bundle.js:36464:23
CompileMetadataResolver.prototype.getNgModuleMetadata http://localhost:4200/vendor.bundle.js:37043:37
JitCompiler.prototype._loadModules http://localhost:4200/vendor.bundle.js:48238:41
JitCompiler.prototype._compileModuleAndComponents http://localhost:4200/vendor.bundle.js:48197:47
JitCompiler.prototype.compileModuleAsync http://localhost:4200/vendor.bundle.js:48159:16
PlatformRef_.prototype._bootstrapModuleWithZone http://localhost:4200/vendor.bundle.js:6792:16
PlatformRef_.prototype.bootstrapModule http://localhost:4200/vendor.bundle.js:6778:16
[104] http://localhost:4200/main.bundle.js:57:1
__webpack_require__ http://localhost:4200/inline.bundle.js:53:12
[265] http://localhost:4200/main.bundle.js:100:18
__webpack_require__ http://localhost:4200/inline.bundle.js:53:12
webpackJsonpCallback http://localhost:4200/inline.bundle.js:24:23
<anonymous>

colltoaction · 2017-04-14T23:11:23Z

I'm not using the CLI, but webpack with @ngtools/webpack plugin. I think you can "eject" your webpack configuration with the CLI if you need to use this workaround.

…

On Fri, Apr 14, 2017, 16:29 Brad Kent ***@***.***> wrote: where is this webpack.config.js file everyone speaks of along with the aotPlugin settings? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5329 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABeg9O6VT8ZXHl7bn2UfC4TJ4KuCPcWjks5rv8kdgaJpZM4MX7At> .

mariussl · 2017-04-19T15:00:14Z

thx @tinchou for the workaround, works perfectly for me (win7x64)

rbarcelos · 2017-04-24T15:57:13Z

Any ETA for when a final fix for this will be deployed? Thanks

hheexx · 2017-04-25T17:05:59Z

Deployed in 1.3.1

mariussl · 2017-04-26T09:36:19Z

thx @hheexx . bugfix confirmed.

filipesilva · 2017-05-23T11:53:41Z

Fixed by #6063

uscbsitric · 2017-11-03T03:00:07Z

I solved min by pressing Ctrl + C on the terminal to end the current npm start,
then ran the entire setup with a npm start.

This error occurred to me when I was switching branches.

angular-automatic-lock-bot · 2019-09-07T15:40:59Z

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

filipesilva assigned hansl Mar 17, 2017

filipesilva added the needs: investigation Requires some digging to determine if action is needed label Mar 17, 2017

This was referenced Mar 27, 2017

I can't build AOT and the error is giving me nothing? #5294

Closed

@ngtools/webpack failing to build, "Can't resolve './../../$$_gendir/..." #5678

Closed

GeorgeKnap mentioned this issue Apr 4, 2017

Build broken unsafecode/ng2-aot#1

Closed

hheexx mentioned this issue Apr 4, 2017

feat(AoT): ✨ ✨ added initial AoT support any many other things TrilonIO/aspnetcore-angular-universal#151

Merged

This was referenced Apr 24, 2017

fix resolve path for windows #6061

Closed

fix(@ngtools/webpack): resolve path windows #6063

Merged

filipesilva closed this as completed May 23, 2017

MarkPieszak mentioned this issue Sep 4, 2017

Lazy loading error when trying to AoT output code to es6 TrilonIO/aspnetcore-angular-universal#394

Closed

angular-automatic-lock-bot bot unassigned hansl Sep 7, 2019

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ERROR in Cannot read property 'getSourceFile' of undefined #5329

ERROR in Cannot read property 'getSourceFile' of undefined #5329

milenkovic commented Mar 9, 2017

Dobryvechir commented Mar 11, 2017

PaybackMan commented Mar 16, 2017

maffelbaffel commented Mar 22, 2017 •

edited

Loading

arlindonatal commented Mar 22, 2017 •

edited

Loading

colltoaction commented Mar 25, 2017

DanWahlin commented Mar 26, 2017

colltoaction commented Mar 26, 2017 via email •

edited

Loading

tavelli commented Apr 12, 2017

colltoaction commented Apr 13, 2017

tavelli commented Apr 13, 2017

hheexx commented Apr 13, 2017

bkdotcom commented Apr 14, 2017 •

edited

Loading

colltoaction commented Apr 14, 2017 via email

mariussl commented Apr 19, 2017

rbarcelos commented Apr 24, 2017 •

edited

Loading

hheexx commented Apr 25, 2017

mariussl commented Apr 26, 2017

filipesilva commented May 23, 2017

uscbsitric commented Nov 3, 2017

angular-automatic-lock-bot bot commented Sep 7, 2019

ERROR in Cannot read property 'getSourceFile' of undefined #5329

ERROR in Cannot read property 'getSourceFile' of undefined #5329

Comments

milenkovic commented Mar 9, 2017

OS?

Versions.

Repro steps.

The log given by the failure.

Dobryvechir commented Mar 11, 2017

PaybackMan commented Mar 16, 2017

maffelbaffel commented Mar 22, 2017 • edited Loading

arlindonatal commented Mar 22, 2017 • edited Loading

colltoaction commented Mar 25, 2017

DanWahlin commented Mar 26, 2017

colltoaction commented Mar 26, 2017 via email • edited Loading

tavelli commented Apr 12, 2017

colltoaction commented Apr 13, 2017

tavelli commented Apr 13, 2017

hheexx commented Apr 13, 2017

bkdotcom commented Apr 14, 2017 • edited Loading

colltoaction commented Apr 14, 2017 via email

mariussl commented Apr 19, 2017

rbarcelos commented Apr 24, 2017 • edited Loading

hheexx commented Apr 25, 2017

mariussl commented Apr 26, 2017

filipesilva commented May 23, 2017

uscbsitric commented Nov 3, 2017

angular-automatic-lock-bot bot commented Sep 7, 2019

maffelbaffel commented Mar 22, 2017 •

edited

Loading

arlindonatal commented Mar 22, 2017 •

edited

Loading

colltoaction commented Mar 26, 2017 via email •

edited

Loading

bkdotcom commented Apr 14, 2017 •

edited

Loading

rbarcelos commented Apr 24, 2017 •

edited

Loading