You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10
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.9-2
node: 6.5.0
os: win32 x64
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
ng new test
cd test
ng serve
browse to localhost:4200 in edge
The log given by the failure. Normally this include a stack trace and some
more information.
App never starts. Stays at Loading..
In console:
SCRIPT65535: Argument not optional
main.bundle.js (65036,13)
Which is zone.js line 556
var fetchPromise = global'fetch';
Don't know if this is the cause or if its an unrelated issue. If debugger tools open in Chrome it stops at that line as well with same problem but after continuing the app loads successfully
Mention any other details that might be useful.
Uninstalled old versions of cli and ran npm cache clean first.
Thanks! We'll be in touch soon.
The text was updated successfully, but these errors were encountered:
Windows 10
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:angular-cli: 1.0.0-beta.11-webpack.9-2
node: 6.5.0
os: win32 x64
do on your code? etc.
ng new test
cd test
ng serve
browse to localhost:4200 in edge
more information.
App never starts. Stays at Loading..
In console:
SCRIPT65535: Argument not optional
main.bundle.js (65036,13)
Which is zone.js line 556
var fetchPromise = global'fetch';
Don't know if this is the cause or if its an unrelated issue. If debugger tools open in Chrome it stops at that line as well with same problem but after continuing the app loads successfully
Uninstalled old versions of cli and ran npm cache clean first.
The text was updated successfully, but these errors were encountered: