Bump @angular/core from 2.1.1 to 15.0.0 in /rzp-ionic2-example

[dependabot[bot]]

Bumps @angular/core from 2.1.1 to 15.0.0.

Release notes

Sourced from @​angular/core's releases.

v15.0.0

15.0.0 (2022-11-16)

Breaking Changes

compiler

• Keyframes names are now prefixed with the component's "scope name". For example, the following keyframes rule in a component definition, whose "scope name" is host-my-cmp:

  @​keyframes foo { ... }

  will become:

  @​keyframes host-my-cmp_foo { ... }

  Any TypeScript/JavaScript code which relied on the names of keyframes rules will no longer match.

  The recommended solutions in this case are to either:

  • change the component's view encapsulation to the None or ShadowDom
  • define keyframes rules in global stylesheets (e.g styles.css)
  • define keyframes rules programmatically in code.

compiler-cli

• Invalid constructors for DI may now report compilation errors

  When a class inherits its constructor from a base class, the compiler may now report an error when that constructor cannot be used for DI purposes. This may either be because the base class is missing an Angular decorator such as @Injectable() or @Directive(), or because the constructor contains parameters which do not have an associated token (such as primitive types like string). These situations used to behave unexpectedly at runtime, where the class may be constructed without any of its constructor parameters, so this is now reported as an error during compilation.

  Any new errors that may be reported because of this change can be resolved either by decorating the base class from which the constructor is inherited, or by adding an explicit constructor to the class for which the error is reported.

• Angular compiler option enableIvy has been removed as Ivy is the only rendering engine.

core

• Angular no longer supports Node.js versions 14.[15-19].x and 16.[10-12].x. Current supported versions of Node.js are 14.20.x, 16.13.x and 18.10.x.
• TypeScript versions older than 4.8 are no longer supported.
• Existing iframe usages may have security-sensitive attributes applied as an attribute or property binding in a template or via host bindings in a directive. Such usages would require an update to ensure compliance with the new stricter rules around iframe bindings.
• Existing iframe usages may have src or srcdoc preceding other attributes. Such usages may need to be updated to ensure compliance with the new stricter rules around iframe bindings.

forms

• setDisabledState will always be called when a ControlValueAccessor is attached. You can opt-out with FormsModule.withConfig or ReactiveFormsModule.withConfig.

localize

• • canParse method has been removed from all translation parsers in @angular/localize/tools. analyze should be used instead.
  • the hint parameter in theparse methods is now mandatory.

router

• Previously, the RouterOutlet would immediately

... (truncated)

Changelog

Sourced from @​angular/core's changelog.

15.0.0 (2022-11-16)

Blog post "Angular v15 is now available".

Breaking Changes

compiler

• Keyframes names are now prefixed with the component's "scope name". For example, the following keyframes rule in a component definition, whose "scope name" is host-my-cmp:

  @​keyframes foo { ... }

  will become:

  @​keyframes host-my-cmp_foo { ... }

  Any TypeScript/JavaScript code which relied on the names of keyframes rules will no longer match.

  The recommended solutions in this case are to either:

  • change the component's view encapsulation to the None or ShadowDom
  • define keyframes rules in global stylesheets (e.g styles.css)
  • define keyframes rules programmatically in code.

compiler-cli

• Invalid constructors for DI may now report compilation errors

  When a class inherits its constructor from a base class, the compiler may now report an error when that constructor cannot be used for DI purposes. This may either be because the base class is missing an Angular decorator such as @Injectable() or @Directive(), or because the constructor contains parameters which do not have an associated token (such as primitive types like string). These situations used to behave unexpectedly at runtime, where the class may be constructed without any of its constructor parameters, so this is now reported as an error during compilation.

  Any new errors that may be reported because of this change can be resolved either by decorating the base class from which the constructor is inherited, or by adding an explicit constructor to the class for which the error is reported.

• Angular compiler option enableIvy has been removed as Ivy is the only rendering engine.

core

• Angular no longer supports Node.js versions 14.[15-19].x and 16.[10-12].x. Current supported versions of Node.js are 14.20.x, 16.13.x and 18.10.x.
• TypeScript versions older than 4.8 are no longer supported.
• Existing iframe usages may have security-sensitive attributes applied as an attribute or property binding in a template or via host bindings in a directive. Such usages would require an update to ensure compliance with the new stricter rules around iframe bindings.
• Existing iframe usages may have src or srcdoc preceding other attributes. Such usages may need to be updated to ensure compliance with the new stricter rules around iframe bindings.

forms

• setDisabledState will always be called when a ControlValueAccessor is attached. You can opt-out with FormsModule.withConfig or ReactiveFormsModule.withConfig.

localize

• • canParse method has been removed from all translation parsers in @angular/localize/tools. analyze should be used instead.
  • the hint parameter in theparse methods is now mandatory.

router

... (truncated)

Commits

• bc97322 docs: add host directives guide (#48057)
• a1b6610 test(common): add e2e tests for the fill mode checks in the NgOptimizedImage ...
• 154ca82 docs(core): add an error details page for unsafe <iframe> bindings (#48027)
• 37a2548 fix(core): add zone.js version 0.12.x as a valid peer dependency (#48002)
• 28f289b fix(core): hardening attribute and property binding rules for <iframe> elemen...
• ae29f98 fix(forms): Runtime error pages must begin with leading zero (#47991)
• 3e490fa refactor(core): remove duplicate createRenderer call (#47981)
• 8f38bba refactor(router): Warn when provideRoutes is used without provideRouter (#47896)
• 173dde7 Revert "fix(core): hardening rules related to the attribute order on iframe e...
• d4b3c0b fix(core): hardening rules related to the attribute order on iframe elements ...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @​angular/core since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #273.