I have deployed the angular 2 app to my test environment. But I'm getting js errors after deployment.
This is what I see on Chrome console when I load the application.
JQMIGRATE: Migrate is installed, version 3.0.0
inline.1523ecb….bundle.js:1 Uncaught TypeError: Cannot read property 'call' of undefined
at r (inline.1523ecb….bundle.js:1)
at Object.542 (main.da73a68….bundle.js:9)
at r (inline.1523ecb….bundle.js:1)
at Object.707 (main.da73a68….bundle.js:11)
at r (inline.1523ecb….bundle.js:1)
at Object.1195 (main.da73a68….bundle.js:1)
at r (inline.1523ecb….bundle.js:1)
at window.webpackJsonp (inline.1523ecb….bundle.js:1)
at main.da73a68….bundle.js:1
A similar error occurred a couple of days of ago but it went away after I rebuilt the angular app a couple of times. From my build logs, I am seeing the following warnings when yarn is installing the dependencies.
yarn -v
yarn install v0.20.3
[1/4] Resolving packages...
[2/4] Fetching packages...
warning [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@ngtools/[email protected]" has unmet peer dependency "@angular/tsc-wrapped@^0.5.0".
[4/4] Building fresh packages...
Done in 63.21s.
yarn
yarn install v0.20.3
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.86s.
npm run build2prod
> [email protected] build2prod C:\projects\iemergent-mms-hblv0\angular
> ng build -prod
0% compilin
However, I don't see any difference in the warnings between a working build and the current failing build.
I currently use appveyor to run the build. Node version is 6.10.0 Yarn version is 0.20.3
I know that this is not a lot to start with. Please let me know if you need any more info.
5 Answer(s)
-
0
Hi,
It is hard to understand problem in this way. You can download Google's canary browser here <a class="postlink" href="https://www.google.com/chrome/browser/canary.html">https://www.google.com/chrome/browser/canary.html</a>. It might show you a better exception message.
Can you try it with that ?
Thanks.
-
0
It shows the same error message. Is there anything else I can try?
-
0
Hi,
Can we access your deployed app somehow ? If so, please send it's address to <a href="mailto:[email protected]">[email protected]</a>.
Thanks.
-
0
I've sent the link to <a href="mailto:[email protected]">[email protected]</a>
-
0
Hi,
Thanks for sharing login infos. This was a browser cache problem if anyone else faces same problem.
