angular-docs-cn/packages/platform-browser
Tobias Bosch a7798f2a93 fix: don’t use the global `ng` at all with closure enhanced optimizations
This is needed as:
- closure declares globals itself for minified names, which sometimes clobber our `ng` global
- we can't declare a closure extern as the namespace `ng` is already used within Google for typings for angularJS (via `goog.provide('ng....')`).
2017-09-27 10:09:56 -07:00
..
animations build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -07:00
src fix: don’t use the global `ng` at all with closure enhanced optimizations 2017-09-27 10:09:56 -07:00
test test(platform-browser): fix mXSS attack test in Canary (#18809) 2017-09-22 13:10:00 -07:00
testing build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -07:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
package.json build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
rollup.config.js build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
tsconfig-build.json fix: don’t use the global `ng` at all with closure enhanced optimizations 2017-09-27 10:09:56 -07:00