Skip to content

fix(deps): update angular monorepo to v10 (major)#112

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-angular-monorepo
Open

fix(deps): update angular monorepo to v10 (major)#112
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-angular-monorepo

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Feb 6, 2020 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@angular/common dependencies major 8.2.14 -> 10.0.3
@angular/compiler devDependencies major 8.2.14 -> 10.0.3
@angular/compiler-cli devDependencies major 8.2.14 -> 10.0.3
@angular/core peerDependencies major >=8.0.0 <10.0.0 -> >=8.0.0 <11.0.0
@angular/core dependencies major 8.2.14 -> 10.0.3
@angular/forms dependencies major 8.2.14 -> 10.0.3
@angular/language-service devDependencies major 8.2.14 -> 10.0.3
@angular/platform-browser dependencies major 8.2.14 -> 10.0.3
@angular/platform-browser-dynamic dependencies major 8.2.14 -> 10.0.3
@angular/router dependencies major 8.2.14 -> 10.0.3

Release Notes

angular/angular

v10.0.3

Compare Source

Bug Fixes
  • core: handle spaces after select and plural ICU keywords (#​37866) (790bb94)

v10.0.2

Compare Source

Bug Fixes
Performance Improvements
  • compiler-cli: fix memory leak in retained incremental state (#​37835) (57a518a)

v10.0.1

Compare Source

Bug Fixes
Performance Improvements
  • compiler-cli: fix regressions in incremental program reuse (#​37690) (96b96fb)

v10.0.0

Compare Source

Release Highlights & Update instructions

To learn about the release highlights and our CLI-powered automated update workflow for your projects please check out the v10 release announcement.

Features
Bug Fixes
Code Refactoring
Performance Improvements
Dependency updates

@​angular/compiler-cli now requires:

  • TypeScript 3.9
BREAKING CHANGES
  • TypeScript 3.6, 3.7 and 3.8 are no longer supported, please update to TypeScript 3.9.
  • core: Angular npm packages no longer contain jsdoc comments
    to support Closure Compiler's advanced optimizations

The support for Closure Compiler in Angular packages has been
experimental and broken for quite some time.

As of TS3.9, Closure is unusable with the JavaScript emit. Please follow
microsoft/TypeScript#​38374 for more
information and updates.

If you used Closure Compiler with Angular in the past, you will likely
be better off consuming Angular packages built from sources directly
rather than consuming the version we publish on npm,
which is primarily optimized for Webpack/Rollup + Terser build pipeline.

As a temporary workaround, you might consider using your current build
pipeline with Closure flag --compilation_level=SIMPLE. This flag
will ensure that your build pipeline produces buildable and
runnable artifacts, at the cost of increased payload size due to
advanced optimizations being disabled.

If you were affected by this change, please help us understand your
needs by leaving a comment on #​37234.

  • core: make generic mandatory for ModuleWithProviders

A generic type parameter has always been required for the ModuleWithProviders pattern to work with Ivy, but prior to this commit, View Engine allowed the generic type to be omitted (though support was officially deprecated).
If you're using ModuleWithProviders without a generic type in your application code, a v10 migration will update your code for you.

However, if you are using View Engine and also depending on a library that omits the generic type, you will now get a build time error similar to:

error TS2314: Generic type 'ModuleWithProviders<T>' requires 1 type argument(s).

In this case, ngcc won't help you (because it's Ivy-only) and the migration only covers application code.
You should contact the library author to fix their library to provide a type parameter when they use this class.

As a workaround, we suggest setting skipLibChecks to false in your tsconfig or updating your app to use Ivy.

  • forms: Number inputs no longer listen to the change event.

Tests which trigger change events need to be updated to trigger input events instead.

The change event was in place to support IE9, as we found that input events were not fired with backspace or cut actions. If you need to maintain IE9 support, you will need to add a change event listener to number inputs and call the onChange method of NumberValueAccessor manually.

Lastly, old versions of WebDriver would synthetically trigger the change event on WebElement.clear and WebElement.sendKeys. If you are using an old version of WebDriver, you may need to update tests to ensure input events are triggered. For example, you could use element.sendKeys(Keys.chord(Keys.CONTROL, "a"), Keys.BACK_SPACE); in place of element.clear().

  • forms: The minLength and maxLength validators now verify that the form control's value has a
    numeric length property, and only validate for length if that's the case.

Previously, falsey values without the length property (such as 0 or
false values) were triggering validation errors. If your code relies on
the old behavior, you can include other validators such as min or
requiredTrue to the list of validators for a particular field.

  • bazel: esm5 and fesm5 format is no longer distributed in
    Angular's npm packages e.g. @​angular/core

If you are not using Angular CLI to build your application or library,
and you need to be able to build es5 artifacts, then you will need to
downlevel the distributed Angular code to es5 on your own.

Angular CLI will automatically downlevel the code to es5 if differential
loading is enabled in the Angular project, so no action is required from
Angular CLI users.

  • core: Warnings about unknown elements are now logged as errors. This won't break your app, but it may trip up tools that expect nothing to be logged via console.error.
  • router: Any resolver which return EMPTY will cancel navigation.
    If you want to allow the navigation to continue, you will need to update the resolvers to emit
    some value, (i.e. defaultIfEmpty(...), of(...), etc).
  • service-worker: Previously, Vary
    headers would be taken into account when retrieving resources from the
    cache, completely preventing the retrieval of cached assets (due to
    ServiceWorker implementation details) and leading to unpredictable
    behavior due to inconsistent/buggy implementations in different
    browsers.

Now, Vary headers are ignored when retrieving resources from the
ServiceWorker caches, which can result in resources being retrieved even
when their headers are different. If your application needs to
differentiate its responses based on request headers, please make sure
the Angular ServiceWorker is configured
to avoid caching the affected resources.

  • common: This change could result in ExpressionChangedAfterItHasBeenChecked errors that
    were not detected before. The error could previously have gone undetected
    because two WrappedValues are considered "equal" in all cases for the purposes
    of the check, even if their respective unwrapped values are not.

Additionally, [val]=(observable | async).someProperty will no longer
trigger change detection if the value of someProperty is identical to
the value in the previous emit. If you need to force change detection,
either update the binding to use an object whose reference changes or
subscribe to the observable and call markForCheck as needed.

  • common: format day-periods that cross midnight

    When formatting a time with the b or B format codes, the rendered
    string was not correctly handling day periods that spanned midnight.
    Instead the logic was falling back to the default case of AM.

    Now the logic has been updated so that it matches times that are within
    a day period that spans midnight, so it will now render the correct
    output, such as at night in the case of English.

    Applications that are using either formatDate() or DatePipe and any
    of the b or B format codes will be affected by this change.

  • router: UrlMatcher's type now reflects that it could always return
    null.

    If you implemented your own Router or Recognizer class, please update it to
    handle matcher returning null.

9.1.11 (2020-06-10)

Reverts
  • elements: fir

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from 387c828 to 7d62ca5 Compare February 12, 2020 18:50
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from 7d62ca5 to 101f089 Compare February 19, 2020 20:10
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 3 times, most recently from b8e436f to 905fca3 Compare March 4, 2020 19:30
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from 905fca3 to a2e8d3d Compare March 11, 2020 00:43
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 2 times, most recently from 3adb037 to 59a4819 Compare March 25, 2020 16:41
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from 59a4819 to 65a1d2a Compare April 7, 2020 23:36
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 2 times, most recently from a0c5c89 to af703a9 Compare April 29, 2020 21:04
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 3 times, most recently from 32c4780 to aa0b4d7 Compare May 13, 2020 22:01
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 2 times, most recently from f698407 to 5f0d23f Compare May 20, 2020 23:23
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch 2 times, most recently from cac4d1a to fa6f78f Compare June 10, 2020 18:26
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from fa6f78f to 8227cb7 Compare July 1, 2020 04:56
@renovate renovate Bot changed the title fix(deps): update angular monorepo to v9 (major) fix(deps): update angular monorepo to v10 (major) Jul 1, 2020
@renovate renovate Bot force-pushed the renovate/major-angular-monorepo branch from 8227cb7 to 90d5113 Compare July 10, 2020 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@renovate-bot