cdc882bd36
The main use case for the generated source maps is to give errors a meaningful context in terms of the original source that the user wrote. Related changes that are included in this commit: * renamed virtual folders used for jit: * ng://<module type>/module.ngfactory.js * ng://<module type>/<comp type>.ngfactory.js * ng://<module type>/<comp type>.html (for inline templates) * error logging: * all errors that happen in templates are logged from the place of the nearest element. * instead of logging error messages and stacks separately, we log the actual error. This is needed so that browsers apply source maps to the stack correctly. * error type and error is logged as one log entry. Note that long-stack-trace zone has a bug that disables source maps for stack traces, see https://github.com/angular/zone.js/issues/661. BREAKING CHANGE: - DebugNode.source no more returns the source location of a node. Closes 14013 |
||
---|---|---|
.github | ||
aio | ||
docs | ||
integration | ||
modules | ||
packages | ||
scripts | ||
tools | ||
.bowerrc | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.nvmrc | ||
.pullapprove.yml | ||
.travis.yml | ||
CHANGELOG.md | ||
COMMITTER.md | ||
CONTRIBUTING.md | ||
DEVELOPER.md | ||
LICENSE | ||
NAMING.md | ||
README.md | ||
SAVED_REPLIES.md | ||
TOOLS.md | ||
TRIAGE_AND_LABELS.md | ||
bower.json | ||
browser-providers.conf.js | ||
build.sh | ||
circle.yml | ||
gulpfile.js | ||
karma-js.conf.js | ||
npm-shrinkwrap.clean.json | ||
npm-shrinkwrap.json | ||
npm-shrinkwrap.readme.md | ||
package.json | ||
protractor-e2e.conf.js | ||
protractor-examples-e2e.conf.js | ||
protractor-perf.conf.js | ||
publish-packages.sh | ||
shims_for_IE.js | ||
test-main.js | ||
test.sh | ||
tslint.json |
README.md
Safari (7+), iOS (7+), Edge (14) and IE mobile (11) are tested on BrowserStack.
Angular
Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript (JS) and other languages.
Quickstart
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.