https://github.com/angular/angular

sort by:
Revision Author Date Message Commit Date
768d4ac release: cut the v12.0.0-rc.2 release 05 May 2021, 22:43:57 UTC
df2ff04 docs: initial commit of content projection topic. (#41143) Content projection is an important part of Angular. However, it has never been documented in the Angular documentation set. This topic attempts to provide the basics of content projection for developers. It is not a comprehensive guide; rather, it is a starting point that we can hopefully expand upon in the future. PR Close #41143 05 May 2021, 20:47:27 UTC
c9f5b07 docs: add documentation for Angular linker (#41485) PR Close #41485 05 May 2021, 20:47:00 UTC
7115139 fix(dev-infra): publish script python check not working on windows (#41943) We recently added a sanity check that ensures that `python` is available for Bazel. The check relies on `/usr/bin/python` to check if python is available w/ the correct version. The problem is that on Windows there is no guarantee that the `/usr/bin` folder exists, so the `ng-dev release publish` command always fails. We fix this by just accessing the `env` binary that is also consulted by scripts executed within Bazel actions. The `env` binary can be assumed exist in the shell's `$PATH` and can point us to Python as if it would be executed within Bazel. PR Close #41943 05 May 2021, 20:46:06 UTC
6109d62 fix(dev-infra): spawned child processes messing with tty output (#41948) Currently we have a common utility method for running commands in a child process. This method pipes all stdout and stderr, but sets the `stdin` to `inherited`. This seemed to work as expected in terms of allowing interactive commands being executed, but it messes with the TTY in Windows (and potentially other platforms) so that colors and prompts no longer work properly. See attached screenshot. We fix this by not inheriting the stdin by default; but exposing a dedicated method for interactive commands. This results in more readable and obvious code too, so it's worth making this change regardless of the TTY issues. PR Close #41948 05 May 2021, 20:45:30 UTC
49c8789 docs: remove ts-node and tslint form dev deps (#41950) A recent commit 3b589030a80e956509c787f6e4c07bb78b529c91 reintroduced these dev deps. They were previously removed by #41826 and #41873 PR Close #41950 05 May 2021, 20:45:01 UTC
829ed3f docs: remove reference to strict mode in local setup (#41952) This is turned on by default in version 12 and prompt has been removed. PR Close #41952 05 May 2021, 20:44:30 UTC
33c9579 refactor(dev-infra): switch away from deprecated platform execution properties (#41941) Bazel no longer recommends the use of `remote_execution_properties` within `platform` definitions. Bazel intends to replace this attribute with an object literal based attribute called `exec_properties`. This simplifies the platform configuration and makes it more readable. Additionally this make inheritance and overriding easier. PR Close #41941 05 May 2021, 04:09:30 UTC
9c45151 docs(common): Corrected the wrong formatting (#41945) Removed the extra backtick character for `getLocaleTimeFormat()` link. PR Close #41945 05 May 2021, 04:08:55 UTC
872204a fix(dev-infra): do not set lts dist tag on packages from release-candidate train (#41946) Currently if a major release-train in the `release-candidate`/`feature-freeze` phase becomes `latest`, we intend to set the NPM LTS dist tag for all packages of the previous major (as the old release train in `latest` moves into LTS phase). The logic for this exists but the release tool sets the NPM dist tag for all packages of the new major. This means that the script might error if a new package is part of the new major; or it could cause a deleted package to not receive the LTS tag properly. PR Close #41946 05 May 2021, 04:07:59 UTC
a257eee docs: add dylhunn to contributors (#41936) PR Close #41936 05 May 2021, 04:06:32 UTC
35ceed2 fix(localize): relax error to warning for missing target (#41944) Some localization workflows want to use the extracted source translation files directy back in the project as a target translation file. The extraction process generates files that only contain "source" messages and not "target" messages. This is actually valid for most translation formats but currently the Angular localization process expects target translation files to always contain target messages and will stop with an error in this case. Now, instead of an error, the translation file loader will log a warning, and then try to falback to a source message, only erroring if this is also missing. Fixes #21690 PR Close #41944 05 May 2021, 04:05:56 UTC
a8ac3be build: fix crash when validating commit messages (#41949) Fixes a crash when running the `ValidateFileModule`. PR Close #41949 05 May 2021, 04:05:20 UTC
8fdac8f fix(compiler-cli): expose the linker as a Babel plugin (#41918) This allows the linker to be used as a true Babel plugin. In a Babel configuration file, include the linker as follows: ```js { plugins: [ '@angular/compiler-cli/linker/babel', ] } ``` or, if you need to specify configuration options: ```js { plugins: [ ['@angular/compiler-cli/linker/babel', {linkerJitMode: true}], ] } ``` PR Close #41918 04 May 2021, 19:43:00 UTC
9759bca fix(core): AsyncPipe now compatible with RxJS 7 (#41590) Adds a fix to make sure that RxJS v7 Observable is compatible with AsyncPipe. This is a typings-only change. For more information see: https://github.com/microsoft/TypeScript/issues/43643 PR Close #41590 04 May 2021, 15:32:51 UTC
384c046 docs: attributes for 'label' and 'input' elements were mixed up (#41827) A label should be 'for' an input, and an 'input' should have an 'id'. PR Close #41827 04 May 2021, 15:32:19 UTC
e453d37 build(docs-infra): upgrade cli command docs sources to 320213975 (#41939) Updating [angular#12.0.x](https://github.com/angular/angular/tree/12.0.x) from [cli-builds#12.0.x](https://github.com/angular/cli-builds/tree/12.0.x). ## Relevant changes in [commit range](https://github.com/angular/cli-builds/compare/d965a67c6...320213975): **Modified** - help/generate.json - help/new.json PR Close #41939 04 May 2021, 15:11:36 UTC
3b9817a docs: update Node.js supported version statement (#41820) Update the statement expressing Angular's supported versions of Node.js. Previously, we stated that the `current` version of Node.js was supported, however Node.js's `current` version maps more closely to what we would term a `next` branch and is not expected meant for usage with production applications. This intention is stated on Node.js Releases page: > Production applications should only use Active LTS or Maintenance LTS releases. PR Close #41820 04 May 2021, 15:10:42 UTC
2d9bfdf docs: add new migration guide to v12 documentation that describes how to migrate older localization ids to new ones (#41828) PR Close #41828 04 May 2021, 15:09:52 UTC
643738a build: remove emojis from github issue templates (#41902) Remove emojis from github issue templates as they are not great for a11y and do not provide great value. PR Close #41902 04 May 2021, 15:09:22 UTC
b7809d5 docs: fix text jargon from DI notes (#41928) PR Close #41928 04 May 2021, 15:08:49 UTC
b5b09dc Revert "fix(language-service): only provide template results on reference requests (#41041)" (#41930) This reverts commit 10aa5641dd85a5eb89f1d1590b9df4119015c29f. Issue resolved upstream https://github.com/microsoft/vscode/issues/117095 PR Close #41930 03 May 2021, 21:27:45 UTC
6edcc17 build: lock file maintenance (#41924) PR Close #41924 03 May 2021, 21:27:06 UTC
ae9c053 docs: update file structure document (#41923) Since angular 11 extra package.json isn't generated and with version 12 strict mode is opt out bases. Updated document to reflect the state Closes #40841. PR Close #41923 03 May 2021, 21:26:38 UTC
3361c19 docs: Remove references to protractor from documentation (#41731) PR Close #41731 03 May 2021, 21:26:09 UTC
cb1fcc8 docs: improve accessibility of form-validation example (#41283) PR Close #41283 03 May 2021, 21:25:14 UTC
9928dc0 build(docs-infra): revert `watchr` to v3.0.1 to restore `docs-watch` performance (#41903) [`watchr` v4.0.0][1] changes the way watched directories are scanned/watched, thus causing a great increase in the consumed CPU and RAM. This affects the performance of the `docs-watch` and transitively `serve-and-sync` npm scripts. (For reference, on my local machine it goes from 0% CPU and 275MB RAM with v3.0.1 to 50% CPU and 10GB RAM with v4+.) This commit pins `watchr` to version 3.0.1 (which is the latest version that does not cause performance issues) and disabled automatic updates via Renovate. [1]: https://github.com/bevry/watchr/releases/tag/v4.0.0 PR Close #41903 03 May 2021, 17:05:31 UTC
f91420c docs: update tagline (#41922) Seems like the tagline has changed on the [Angular Twitter account](https://twitter.com/angular) and angular.io. This change makes this doc in line with those two resources. PR Close #41922 03 May 2021, 17:04:07 UTC
426c0a7 docs(forms): reduce ambiguity in forms data flow wording (#41900) PR Close #41900 03 May 2021, 17:01:17 UTC
922a602 fix(common): add right ContentType for boolean values with HttpClient request body(#38924) (#41885) currently a boolean as body is seen as text/plain, where is should be seen as application/json, since it is valid JSON, like numbers. PR Close #41885 03 May 2021, 17:00:19 UTC
d59330b docs: Update link to Testing Angular online book (#41906) The book has moved to a its own domain. PR Close #41906 30 April 2021, 21:34:51 UTC
cc19993 fix(dev-infra): remove getBaseDir method from GitClient (#41898) Remove the getBaseDir method from GitClient as the baseDir is determined once during construction and does not need to be rediscovered. The property access should always be used. PR Close #41898 30 April 2021, 21:33:59 UTC
c97d217 test: update `runtime-es2015` sizes follow CLI updates (#41871) These size changes are caused by a new Webpack version. PR Close #41871 30 April 2021, 21:31:09 UTC
d97d127 build: update angular (#41871) PR Close #41871 30 April 2021, 21:31:09 UTC
7255fbc docs: remove references to Trusted Types due to incompatibility with Webpack 5 (#41754) PR Close #41754 30 April 2021, 21:30:31 UTC
8da896f build(docs-infra): upgrade cli command docs sources to d965a67c6 (#41895) Updating [angular#12.0.x](https://github.com/angular/angular/tree/12.0.x) from [cli-builds#12.0.x](https://github.com/angular/cli-builds/tree/12.0.x). ## Relevant changes in [commit range](https://github.com/angular/cli-builds/compare/54ce436c9...d965a67c6): **Modified** - help/add.json - help/analytics.json - help/deploy.json - help/e2e.json - help/help.json - help/lint.json - help/new.json - help/run.json - help/test.json PR Close #41895 30 April 2021, 21:25:47 UTC
525d53a build: update all non-major dependencies (#41884) PR Close #41884 30 April 2021, 21:25:09 UTC
73c6c64 fix(core): handle multiple i18n attributes with expression bindings (#41882) When there are multiple attributes that are marked for i18n translation, which contain expression bindings, we were generating i18n update op-codes that did not accurately map to the correct value to be bound in the lView. Each attribute's bindings were relative to the start of the lView first attributes values rather than to their own. This fix passes the current binding index to `generateBindingUpdateOpCodes()` when processing i18n attributes to account for this. Fixes #41869 PR Close #41882 30 April 2021, 21:20:15 UTC
36a0358 fix(docs-infra): switch over to img[loading=lazy] for front page images (#34900) This should speed up the perceived loading latency as the image loading won't block rendering. https://addyosmani.com/blog/lazy-loading/ PR Close #34900 30 April 2021, 21:16:25 UTC
01cc995 fix(animations): ensure consistent transition namespace ordering (#19854) When including a component in a template, the component's host element is immediately appended as child of the parent node upon creation. Hence, `hostElement.parentNode` will be a valid reference. However, if the parent component is being inserted as an embedded view—through `ngIf` for example—then the parent's node itself will not have been inserted yet. This means that we cannot properly determine the position of the transition namespace, as any `containsElement` check will return false given that the partial DOM tree has not been inserted yet, even though it will be contained within an existing transition namespace once the partial tree is attached. This commit fixes the issue by not just looking at the existence of a parent node, but rather a more extensive check using the driver's `containsElement` method. PR Close #19854 30 April 2021, 21:15:49 UTC
75bb931 fix(compiler-cli): prefer non-aliased exports in reference emitters (#41866) This commit changes the reference emitters in the Ivy compiler to prefer non-aliased exports if they exist. This avoids selecting "private exports" that may not be stable, e.g. the reexports that have been added by the View Engine compiler. Such reexports are not stable and are therefore not suitable to be emitted into partial compilations, as the output of partial compilations should only reference stable symbols from upstream libraries. An alternative solution has been considered where ViewEngine-generated exports would gain a certain prefix, such that the Ivy compiler could just exclude those exports (see #41443). However, that solution would be insufficient in case a library is built using partial compilation and while depending itself on a VE-compiled library from earlier versions of Angular, where the magic prefix would be missing. For such libraries, ngcc would have generated reexports using the declared name if not already present so this change does result in choosing the correct export. Because ngcc always generates reexports using the declared name even if an aliased export is present, this change causes those ngcc-generated exports to be chosen in downstream libraries using partial compilation. This is unfortunate as it means that the declared names become effectively public even if the library author was intentionally exporting it using an alias. This commit does not address this problem; it is expected that this should not result in widespread issues across the library ecosystem. Fixes #41277 PR Close #41866 30 April 2021, 21:15:11 UTC
88ba98a build: exclude compiler compliance tests from Saucelabs tests (#41866) The legacy-unit-tests-saucelabs job does not need to compile the compiler compliance tests as they are not used in those tests. Since the compliance tests can be configured to use specific compiler options, the generic tsconfig that is used in legacy-unit-tests-saucelabs may not succeed to compile the compliance tests so this commit excludes those source files. PR Close #41866 30 April 2021, 21:15:11 UTC
9346d61 perf(core): minor improvements to listener instructions (#41807) Makes the following improvements to the listener instructions to make them slightly smaller and more memory-efficient. 1. Removes the default value from the `useCapture` parameter since it generates more code than just castint to `false`. 2. Removes the `useCapture` and `eventTargetResolver` parameters from `ɵɵsyntheticHostListener` since they won't be generated by the compiler, as far as I can tell. 3. Makes it so that we don't have to return a target name from a `GlobalTargetResolver`. This allows us to save on some memory, because we can return a reference to the target without having to wrap it in an object literal. DEPRECATIONS: `EventManagerPlugin.getGlobalEventTarget` is now deprecated and won't be called from Ivy code anymore. Global events will go through `addEventListener`. PR Close #41807 30 April 2021, 21:14:00 UTC
1c0db8c Revert "perf(core): avoid storing LView in __ngContext__ (#41358)" (#41901) This reverts commit 18b33e79d3d64f98f80838503e802d0369fcdb16. PR Close #41901 30 April 2021, 21:12:53 UTC
be9b19e Revert "build: update dependency karma to v6 (#41696)" (#41904) This reverts commit 595a75cda4dc38a3e55c6fbfc97ffad275ab5990. PR Close #41904 30 April 2021, 20:30:16 UTC
0255a2c docs(docs-infra): fix handling of client-side errors in networking (#36608) Previously example for handling client-side errors in networking didn't work when there was no Internet connection. Caught error is ProgressEvent in such case, not ErrorEvent and error.error.message is undefined. PR Close #36608 29 April 2021, 20:51:44 UTC
39e1818 test(core): make tests more resilient to header offset changes (#41883) Updates some tests where values related to the `HEADER_OFFSET` are hardcoded, causing them to break when the offset is updated. This comes up once in a while during refactorings and these changes should save us some time in the future. PR Close #41883 29 April 2021, 20:51:07 UTC
b33dc4e ci: replace `matchCurrentVersion` RegExp negate with semver version (#41886) While RegExp negation should work as per documentation https://docs.renovatebot.com/configuration-options/#matchcurrentversion it appears that in this case it is not working. See the following commit https://github.com/angular/angular/pull/41884/commits/076f13da867d2bc46b41bd49f09ccb49e00a4095, therefore we work around this by using a semver version that excludes anything which doesn't match `>= 1`. PR Close #41886 29 April 2021, 20:50:25 UTC
c7b40ba ci: changes to `packages/common/http` should not require `fw-common` approval (#41887) Currently when the change is made to the code inside the `packages/common/http` folder, both `fw-http` and `fw-common` group members are assigned for review. However only `fw-http` is required and should be sufficient. This commit updates the PullApprove config to exclude `packages/common/http` path from the list of folders that `fw-common` "owns". PR Close #41887 29 April 2021, 20:49:39 UTC
77b77ff ci: only run `publish_snapshot` when not PR (#41877) Currently, the non forked PRs such as Renovate will run `publish_snapshot` because `CIRCLE_PR_NUMBER` is not defined for PRs which are opened from non forked repos. Instead we add a filter to only run `publish_snapshot` on releasable branches. Example of run were the mentioned variable is not defined https://app.circleci.com/pipelines/github/angular/angular/32093/workflows/7c8c4cfc-e6f6-44fc-a6dc-a82a6ac862db/jobs/976611 PR Close #41877 29 April 2021, 17:16:05 UTC
6e66916 docs: remove ts-node form dev deps (#41873) Follow-up to #41826 The CLI now no longer installs `ts-node` since Protractor has been removed. See https://github.com/angular/angular-cli/pull/20601 for the relevant PR in angular-cli. This change has been released in the CLI v12.0.0-rc.1 PR Close #41873 29 April 2021, 17:08:14 UTC
25333db ci: exclude packages which don't have a major from being batched (#41865) With this change we exclude packages that are not stable yet from being batched in the `all non-major dependencies`. The reason behind this is that these package can contain breaking changes in minor versions, hence they should be treated as breaking and a PR should be opened separately. PR Close #41865 29 April 2021, 17:07:27 UTC
63ad5bf ci: enable Renovate for remark packages (#41865) Automatic updates of these packages is now possible as AIO tooling has been updated to use the latest version. See: https://github.com/angular/angular/pull/41721 PR Close #41865 29 April 2021, 17:07:27 UTC
af43162 docs: correct toh router tutorial (#41859) * `SelectivePreloadingStrategyService` is already provided in the root module, so it should not be added to `AppRoutingModule` providers array PR Close #41859 29 April 2021, 17:05:32 UTC
d70f831 build: update dependency karma to v6 (#41696) PR Close #41696 29 April 2021, 17:04:24 UTC
ede0cfe docs: Edits to remove jargon (#41536) PR Close #41536 28 April 2021, 22:11:34 UTC
45792f1 docs: remove tslint, codelyzer & protractor from dev deps (#41826) TSLint and Codelyzer were deprecated in v11. Protractor is no longer installed by default in new projects in v12. PR Close #41826 28 April 2021, 21:33:14 UTC
f629f9f docs: imrpove accessibility of lifecycle hooks example (#41071) PR Close #41071 28 April 2021, 21:26:37 UTC
d8fcb99 docs: add error page for NG6999 (#41708) Adds page for NG6999 error for VE builds that attempt to consume an Ivy-compiled library. Will go here: https://angular.io/errors/NG6999 PR Close #41708 28 April 2021, 21:22:46 UTC
c691b66 docs: remove mention of scheduleTick in markForCheck (#41845) markForCheck doesn't call scheduleTick, thus I removed the comment which mentioned this. PR Close #41845 28 April 2021, 19:34:51 UTC
d7763a9 build(docs-infra): update to latest puppeteer (#41764) The updates to WebDriver required an update to puppeteer to ensure that the correct Chromium was downloaded. PR Close #41764 28 April 2021, 19:33:21 UTC
0aa9239 build(docs-infra): add `assert` polyfill (#41764) With this change we add the `assert` polyfill which is required because `timezone-mock` is a Node.JS library which is being used in Browser. PR Close #41764 28 April 2021, 19:33:21 UTC
4981c28 build(docs-infra): remove `src/generated` from `ng test` configuration (#41764) Assets are stored in memory during `ng test` hence since `src/generated` are unused we shouldn't include them. PR Close #41764 28 April 2021, 19:33:21 UTC
0dcadab build(docs-infra): update angular packages to `12.0.0-rc.0` (#41764) Update Angular packages to `12.0.0-rc.0` PR Close #41764 28 April 2021, 19:33:21 UTC
eed5ada build: update angular package to `12.0.0-rc.0` (#41764) Update Angular packages to `12.0.0-rc.0` PR Close #41764 28 April 2021, 19:33:20 UTC
98de217 release: cut the v12.0.0-rc.1 release (#41864) 28 April 2021, 18:58:23 UTC
a66421e ci: re-enable the `@angular/components` unit tests (#41816) Previously, the `components-repo-unit-tests` CI job was temporarily disabled due to a version mismatch between the `rules_nodejs` dependency version on the two repos (angular/angular and angular/components). Now that both repos have been updated to a `rules_nodejs` version >=2.0.0, we can re-enable the job and have `@angular/components` unit tests run on every build. PR Close #41816 28 April 2021, 16:57:50 UTC
77a5157 build: update remark packages (#41721) This commit updates the `remark` packages to v12 instead of the latest (v13), because v13 is a major breaking change that requires more investigation and work. More specifically, v13 replaces the internals of `remark` with a new CommonMark-compliant parser. (See their [release notes][1] for more info.) This change causes our old `remark` plugins (in [renderMarkdown.js][2]) to stop working. [1]: https://github.com/remarkjs/remark/releases/tag/13.0.0 [2]: https://github.com/angular/angular/blob/d42019d4128ca0d9f233a085bfe838f93f8d0412/aio/tools/transforms/remark-package/services/renderMarkdown.js#L17-L24 PR Close #41721 28 April 2021, 16:27:23 UTC
624dc4c fix(dev-infra): replace `chalk` require with namespace import (#41847) Since we now use version 4 we can use namespace imports and leverage in build types. PR Close #41847 28 April 2021, 16:22:31 UTC
73cdd8f build: update dependency chalk to v4 (#41847) PR Close #41847 28 April 2021, 16:22:31 UTC
3fdc261 fix(dev-infra): correctly detect prettier config (#41860) This commit uses the correct property name (`prettier` vs `pretter`) to check whether prettier is enabled via the config. (It also fixes some typos in `dev-infra`.) PR Close #41860 28 April 2021, 16:21:10 UTC
dfff5d3 fix(docs-infra): do not redirect disambiguated URLs (#41842) In #41788, logic was added to disambiguate case-insensitively equal docs paths/URLs. This process includes appending a `-\d+` suffix to some paths/URLs (for example, `/.../inject-1`). Unfortunately, some of the Firebase redirects configured in `firebase.json` would match these URLs and redirect them to non-existing paths. Example failures: [stable][1], [next][2] NOTE: This was not picked up in the regular CI tests run for PRs, because the local devserver and the preview server used to test PRs do not support Firebase-like redirects. This commit fixes this by ensuring these disambiguated paths/URLs are not matched by the redirect rules by checking whether the part of the suffix after the `-` contains any numeric digits. While this check is not ideal, it should be good enough for our purpose, since the legacy URLs that we do want to redirect contain suffixes such as `-class`, `-function` and thus no numeric digits. [1]: https://circleci.com/gh/angular/angular/974345 [2]: https://circleci.com/gh/angular/angular/974346 PR Close #41842 27 April 2021, 21:05:23 UTC
7270a1f build(docs-infra): take disambiguated doc paths into account when generating the sitemap (#41842) In ##41788, the `disambiguateDocsPathsProcessor` was introduced to fix an issue with case-insensitively equal paths. This processor may alter the paths of some docs and thus their final URL in the app. Previously, both the `disambiguateDocPathsProcessor` and the `createSitemap` processor (which relies on the docs' computed paths to generate the sitemap file) were configured to run before the "rendering-docs" phase. However, this resulted in the `disambiguateDocPathsProcessor`'s running after `createSitemap`, which meant that the sitemap did not include the updated doc paths. This commit fixes it by ensuring that the `disambiguateDocPathsProcessor` is explicitly run before the `createSitemap` processor, so that the latter will be able to take into account any changes made by the former. PR Close #41842 27 April 2021, 21:05:23 UTC
849d11d test(docs-infra): make it easier to identify the failing URL in `testFirebaseRedirection.spec.ts` (#41842) This commit includes the URL under test in the test description in `testFirebaseRedirection.spec.ts` to make it easier to identify the affected URL when a test fails. It also avoids unnecessarily creating multiple `FirebaseRedirector` instances by sharing instances between tests. PR Close #41842 27 April 2021, 21:05:23 UTC
05a9a76 test(docs-infra): update `firebase-test-utils` to support regex-based redirects (#41842) This commit updates the utilities in `firebase-test-utils/` to also support testing Firebase redirects that are configured using regular expressions (via the `regex` property). See the [Firebase docs][1] for more details. [1]: https://firebase.google.com/docs/hosting/full-config#redirects PR Close #41842 27 April 2021, 21:05:23 UTC
dc708c1 refactor(docs-infra): prepare `firebase-test-utils` for accepting regex-based redirects (#41842) Currently, the utilities for testing Firebase redirects assume that the redirects are configured using the glob-based `source` property. However, Firebase also supports configuring redirects using regular expressions (via the `regex` property). See the [Firebase docs][1] for more details. This commit refactors the utilities in `firebase-test-utils/` to make it easy to add support for such regex-based redirect configurations. [1]: https://firebase.google.com/docs/hosting/full-config#redirects PR Close #41842 27 April 2021, 21:05:23 UTC
163e044 test(docs-infra): fix `create-example` tests on Windows (#41842) Previously, the tests in `create-example.spec.ts` made assertions using some hard-coded absolute paths (something like `/foo/bar`). This caused the tests to fail on Windows, where the absolute paths are prefixed with the drive letter (something like `C:/foo/bar`). This commit uses `path.resolve()` to ensure paths are converted to the format used on the current OS. PR Close #41842 27 April 2021, 21:05:23 UTC
30db14b ci: several updates to renovate configuration (#41834) - Since the PRs needs to get reviewed we replace label `action: merge` with `action: review`. - Add `remark` and `remark-html` to `ignoreDeps` since they require some work to bump. - Remove `commitMessage`, Renovate now creates better commit messages. - Group all non-major dependencies into a single group and schedule the updates for every Thursday PR Close #41834 27 April 2021, 20:26:04 UTC
947b451 feat(dev-infra): create the prettier formatter for ng-dev format tooling (#41824) Add support to use prettier for formatting using `ng-dev format`. PR Close #41824 27 April 2021, 19:23:08 UTC
0e09009 ci: add Zach Arend to pullapprove groups (#41839) Add Zach Arend to the pullapprove groups for public api, size tracking, and circular deps. PR Close #41839 27 April 2021, 18:35:06 UTC
b0a58bd fix(dev-infra): add github token requirement for discover-new-conflicts (#41825) Add the github token option/requirement for the pr discover-new-conflicts command. PR Close #41825 27 April 2021, 17:23:19 UTC
459c4fd docs: remove the section "Using components vs services from other modules" (#41835) This section states that "Importing a module with services means that you will have a new instance of that service". This is only true for lazy-loaded `NgModules`. For non-lazy-loaded modules, my understanding is that the providers arrays are flattened into the root injector meaning that importing a module with a service doesn't create a new instance of that service. PR Close #41835 27 April 2021, 17:16:52 UTC
f9af984 build(docs-infra): update dgeni-packages to fix version list (#41832) The current version was not being computed correctly for next and rc deployments of the angular.io website. Fixes #41829 PR Close #41832 27 April 2021, 17:15:29 UTC
511f75f build: update @types/jasmine to version 3.6.10 (#41830) PR Close #41830 27 April 2021, 17:14:09 UTC
2a11cda fix(compiler): strip scoped selectors from `@font-face` rules (#41815) `@font-face` rules cannot contain nested selectors. Nor can they be nested under a selector. Normally this would be a syntax error by the author of the styles. But in some rare cases, such as importing styles from a library, and applying `:host ::ng-deep` to the imported styles, we can end up with broken css if the imported styles happen to contain `@font-face` rules. This commit works around this problem by sanitizing such cases (erasing any scoping selectors) during emulated ShadowDOM encapsulation style processing. Fixes #41751 PR Close #41815 27 April 2021, 16:12:31 UTC
f9c1f08 fix(core): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
10c4523 fix(upgrade): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
6b823d7 fix(service-worker): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
0067edd fix(router): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
4b9d4fa fix(platform-server): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
ea05cfd fix(platform-browser): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
bc45029 fix(platform-browser-dynamic): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
658ed1f fix(localize): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:15 UTC
9b6198c fix(language-service): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
dc975ba fix(forms): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
4f5d094 fix(elements): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
bae8126 fix(compiler): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
5b463f4 fix(compiler-cli): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
f2b6fd8 fix(common): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
8503246 fix(bazel): update supported range of node versions to only include LTS versions (#41822) Update the supported range of node versions for Angular to only include supported LTS versions. PR Close #41822 26 April 2021, 22:21:14 UTC
back to top