Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update frontendDevDependencies (major) #519

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular-devkit/build-angular ^17.0.8 -> ^18.0.0 age adoption passing confidence
@angular/cli ^17.0.8 -> ^18.0.0 age adoption passing confidence
@angular/compiler-cli (source) ^17.0.8 -> ^18.0.0 age adoption passing confidence
@types/jasmine (source) ~3.10.0 -> ~5.1.0 age adoption passing confidence
jasmine-core (source) 4.0.0 -> 5.1.2 age adoption passing confidence
karma-jasmine ~4.0.0 -> ~5.1.0 age adoption passing confidence
karma-jasmine-html-reporter ~1.7.0 -> ~2.1.0 age adoption passing confidence

Release Notes

angular/angular-cli (@​angular-devkit/build-angular)

v18.0.1

Compare Source

v18.0.0

Compare Source

Breaking Changes

@​angular/cli
  • The ng doc command has been removed without a replacement. To perform searches, please visit www.angular.dev
  • Node.js support for versions <18.19.1 and <20.11.1 has been removed.
@​angular-devkit/build-angular
  • By default, the index.html file is no longer emitted in the browser directory when using the application builder with SSR. Instead, an index.csr.html file is emitted. This change is implemented because in many cases server and cloud providers incorrectly treat the index.html file as a statically generated page. If you still require the old behavior, you can use the index option to specify the output file name.

    "architect": {
      "build": {
        "builder": "@&#8203;angular-devkit/build-angular:application",
        "options": {
          "outputPath": "dist/my-app",
          "index": {
            "input": "src/index.html",
            "output": "index.html"
          }
        }
      }
    }
  • The support for the legacy Sass build pipeline, previously accessible via NG_BUILD_LEGACY_SASS when utilizing webpack-based builders, has been removed.

Deprecations

@​angular-devkit/schematics
  • NodePackageLinkTask in @angular-devkit/schematics. A custom task should be created instead.
@​angular/cli
Commit Type Description
ac3019570 feat add ng dev alias to ng serve
4087728c3 feat support for Node.js v22
41ab6c8c3 fix add --version option
df4dde95d fix add @angular/build package to update group list
1039f6d79 fix change update guide link to angular.dev
f4670fcb1 fix eliminate prompts during ng version command
a99ec6a54 fix keep cli package first in update package group metadata
dd786d495 fix only add --version option on default command
03eee0545 refactor remove ng doc command
c7b208555 refactor remove support for Node.js versions <18.19.1 and <20.11.1
@​schematics/angular
Commit Type Description
b2ac5fac7 feat allow application migration to use new build package in projects where possible
6530aa11b feat replace assets with public directory
725883713 feat use eventCoalescing option by default (standalone bootstrap)
508d97da7 feat use ngZoneEventCoalescing option by default (module bootstrap)
f452589e2 feat use TypeScript bundler module resolution for new projects
95a4d6ee5 fix add less dependency in application migration if needed
c46aa084f fix add postcss dependency in application migration if needed
157329384 fix add spaces around eventCoalescing option
23cc337aa fix keep deployUrl option when migrating to application builder
@​angular-devkit/architect
Commit Type Description
ddd08efef fix resolve builder aliases from containing package
@​angular-devkit/build-angular
Commit Type Description
53c319aaa feat add support for the poll option in the library builder
83d1d233a feat enhance Sass rebasing importer for resources URL defined in variables and handling of external paths
d51cb598a feat inject event-dispatch in SSR HTML page
0b03829bc feat move i18n extraction for application builder to new build system package
4ffe07aa2 feat move Vite-based dev-server for application builder to new build system package
d1c632af9 feat support native async/await when app is zoneless
37fc7f0cc fix disable Vite prebundling when script optimizations are enabled
2acf95a94 fix do not generate an index.html file in the browser directory when using SSR.
8a54875cb fix handle wrapping of class expressions emitted by esbuild
97973059e refactor remove Sass legacy implementation
@​angular-devkit/schematics
Commit Type Description
797584583 refactor deprecate NodePackageLinkTask
@​angular/build
Commit Type Description
810d213e1 feat introduce new official build system package
b7a0792b3 fix add a maximum rendering timeout for SSG
411115303 fix add console note about development server raw file size
921fa7cf4 fix add missing ansi-colors and picomatch dependencies
791cf75af fix check both potential build packages in Angular version check
4d7cd5e3e fix correctly wrap class expressions with static properties or blocks emitted by esbuild
57f448a0f fix decode URL pathname decoding during SSG fetch
940e382db fix disable Vite prebundling when script optimizations are enabled
70dbc7a6e fix emit error for invalid self-closing element in index HTML
44b401747 fix ensure input index HTML file triggers rebuilds when changed
dff4deaeb fix ensure recreated files are watched
17931166d fix format sizes using decimal byte units consistently
2085365e0 fix only generate shallow preload links for initial files
33cd47c85 fix properly configure headers for media resources and HTML page
d10fece2c fix properly rebase Sass url() values with leading interpolations
3f2963835 perf add persistent caching of JavaScript transformations
a15eb7d1c perf improve rebuild time for file loader usage with prebundling

v17.3.8

Compare Source

17.3.8 (2024-05-22)
@​angular/cli
Commit Description
fix - 3ada6eb52 clarify optional migration instructions during ng update
@​angular-devkit/schematics
Commit Description
fix - 4b6ba8df1 SchematicTestRunner.runExternalSchematic fails with "The encoded data was not valid for encoding utf-8"

v17.3.7

Compare Source

v17.3.6

Compare Source

@​angular-devkit/build-angular
Commit Type Description
dcec59799 fix properly configure headers for media resources and HTML page

v17.3.5

Compare Source

v17.3.4

Compare Source

@​angular-devkit/build-angular
Commit Type Description
1128bdd64 fix ensure esbuild-based builders exclusively produce ESM output

v17.3.3

Compare Source

@​schematics/angular
Commit Type Description
a673baf5c fix Revert "fix(@​schematics/angular): rename SSR port env variable"

v17.3.2

Compare Source

@​schematics/angular
Commit Type Description
935f931ee fix rename SSR port env variable
@​angular-devkit/build-angular
Commit Type Description
c9d436000 fix Internal server error: Invalid URL when using a non localhost IP
59fba38ec fix ensure proper resolution of linked SCSS files
27dd8f208 fix service-worker references non-existent named index output
c12907d92 fix update webpack-dev-middleware to 6.1.2

v17.3.1

Compare Source

17.3.1 (2024-03-20)

@​schematics/angular
Commit Description
fix - 198ca9afc improve Sass format clarity for application style option
@​angular-devkit/build-angular
Commit Description
fix - 2809971a5 only generate server directory when SSR is enabled
fix - 3f601a14e typo in allowedHosts warning for unsupported vite options
perf - 79c44adac avoid transforming empty component stylesheets
perf - cc3167f30 reduce build times for apps with a large number of components when utilizing esbuild-based builders

v17.3.0

Compare Source

@​schematics/angular
Commit Type Description
5ab71fc92 feat update CSS/Sass import/use specifiers in application migration
@​angular-devkit/build-angular
Commit Type Description
9ca3a5450 feat add deployUrl to application builder
3821344da fix ensure proper display of build logs in the presence of warnings or errors
de2d05049 fix provide better error message when server option is required but missing

v17.2.3

Compare Source

@​angular-devkit/build-angular
Commit Type Description
7cc8261fd fix avoid implicit CSS file extensions when resolving
259ec72d5 fix avoid marking component styles as media with no output media directory
faffdfdce fix disable deployUrl when using vite dev-server

v17.2.2

Compare Source

@​angular-devkit/build-angular
Commit Type Description
3394d3cf1 fix ensure all related stylesheets are rebuilt when an import changes

v17.2.1

Compare Source

@​angular-devkit/build-angular
Commit Type Description
9e7c47b59 fix allow mts and cts file replacement
f2a2e9287 fix provide Vite client code source map when loading

v17.2.0

Compare Source

@​angular/cli
Commit Type Description
b3e206741 feat add support to bun package manager
@​schematics/angular
Commit Type Description
03e1aa790 feat add support to bun package manager
@​angular-devkit/build-angular
Commit Type Description
7f57123fd feat add define build option to application builder
f4f535653 feat add JSON build logs when using the application builder
b59f663e5 feat allow control of Vite-based development server prebundling
8f47f1e96 feat provide default and abbreviated build target support for dev-server and extract-i18n
7a12074dc feat provide option to allow automatically cleaning the terminal screen during rebuilds
7c522aa87 feat support using custom postcss configuration with application builder
476a68daa fix add output location in build stats
5e6f1a9f4 fix avoid preloading server chunks
41ea985f9 fix display server bundles in build stats
d493609d3 fix downgrade copy-webpack-plugin to workaround Node.js support issue
8d5af1d5c fix ensure correct .html served with Vite dev-server
944cbcdb1 fix limit the number of lazy chunks visible in the stats table
905e13633 fix support string as plugin option in custom postcss plugin config
@​angular-devkit/schematics
Commit Type Description
da1c38c48 fix add bun to known package managers
@​angular/create
Commit Type Description
600498f2c feat add support to bun package manager

v17.1.4

Compare Source

@​angular/cli
Commit Type Description
6d2168db9 fix prevent BOM errors in package.json during ng update
@​angular-devkit/build-angular
Commit Type Description
bf42d6df2 fix bypass Vite prebundling for absolute URL imports

v17.1.3

Compare Source

@​angular-devkit/build-angular
Commit Type Description
3de3aa170 fix allow ./ baseHref when using vite based server
17f47a3c9 fix ensure WebWorker main entry is used in output code

v17.1.2

Compare Source

@​angular-devkit/build-angular
Commit Type Description
6815f13e3 fix add required modules as externals imports
a0e306098 fix correctly handle glob negation in proxy config when using vite
235c8403a fix handle regular expressions in proxy config when using Vite
5332e5b2e fix resolve absolute output-path when using esbuild based builders
3deb0d4a1 fix return 404 for assets that are not found

v17.1.1

Compare Source

@​angular/cli
Commit Type Description
8ebb754c2 fix update regex to validate the project-name
@​schematics/angular
Commit Type Description
35ebf1efd fix retain trailing comma when adding providers to app config
@​angular-devkit/build-angular
Commit Type Description
88de1da92 fix ENOENT: no such file or directory on Windows during component rebuild
4e2586aeb fix allow package file loader option with Vite prebundling
aca1cfcda fix do not add internal CSS resources files in watch
53258f617 fix handle load event for multiple stylesheets and CSP nonces
412fe6ec6 fix pre-transform error when using vite with SSR
45dea6f44 fix provide actionable error message when server bundle is missing default export
4e2b23f03 fix update dependency vite to v5.0.12
@​angular/ssr
Commit Type Description
02d9d84c5 fix handle load event for multiple stylesheets and CSP nonces

v17.1.0

Compare Source

@​schematics/angular
Commit Type Description
b513d89b7 feat add optional migration to use application builder
a708dccff feat update SSR and application builder migration schematics to work with new outputPath
4469e481f fix do not trigger NPM install when using ---skip-install and --ssr
@​angular-devkit/build-angular
Commit Type Description
e0b274b8f feat add option to retain CSS special comments in global styles
204794c4f feat add support for --no-browsers in karma builder
4784155bd feat add wildcard option for allowedCommonJsDependencies
3b93df42d feat allow configuring loaders for custom file extensions in application builder
cc246d50e feat allow customization of output locations
15a669c1e feat allowing control of index HTML initial preload generation
47a064b14 feat emit external sourcemaps for component styles
68dae539a feat initial experimental implementation of @web/test-runner builder
f6e67df1c feat inline Google and Adobe fonts located in stylesheets
364a16b7a feat move browser-sync as optional dependency
ccba849e4 feat support keyboard command shortcuts in application dev server
329d80075 fix alllow OPTIONS requests to be proxied when using vite
49ed9a26c fix emit error when using prerender and app-shell builders with application builder
6473b0160 fix ensure all configured assets can be served by dev server
874e576b5 fix filter explicit external dependencies for Vite prebundling
2a02b1320 fix fix normalization of the application builder extensions
9906ab7b4 fix normalize asset source locations in Vite-based development server
ceffafe1a fix provide better error messages for failed file reads
6d7fdb952 fix show diagnostic messages after build stats
4e1f0e44d fix the request url "..." is outside of Vite serving allow list for all assets
bd26a18e7 fix typo in preloadInitial option description
125fb779f perf reduce TypeScript JSDoc parsing in application builder
angular/angular (@​angular/compiler-cli)

v18.0.0

Compare Source

Breaking Changes

animations
  • Deprecated matchesElement method has been removed from AnimationDriver as it is unused.
common
  • The deprecated isPlatformWorkerUi and isPlatformWorkerApp have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.
compiler
  • Angular only supports writable expressions inside of two-way bindings.
compiler-cli
    • Angular no longer supports TypeScript versions older than 5.4.
core
  • OnPush views at the root of the application need to
    be marked dirty for their host bindings to refresh. Previously, the host
    bindings were refreshed for all root views without respecting the
    OnPush change detection strategy.

  • OnPush views at the root of the application need to
    be marked dirty for their host bindings to refresh. Previously, the host
    bindings were refreshed for all root views without respecting the
    OnPush change detection strategy.

  • The ComponentFixture autoDetect feature will no
    longer refresh the component's host view when the component is OnPush
    and not marked dirty. This exposes existing issues in components which
    claim to be OnPush but do not correctly call markForCheck when they
    need to be refreshed. If this change causes test failures, the easiest
    fix is to change the component to ChangeDetectionStrategy.Default.

  • ComponentFixture.whenStable now matches the
    ApplicationRef.isStable observable. Prior to this change, stability
    of the fixture did not include everything that was considered in
    ApplicationRef. whenStable of the fixture will now include unfinished
    router navigations and unfinished HttpClient requests. This will cause
    tests that await the whenStable promise to time out when there are
    incomplete requests. To fix this, remove the whenStable,
    instead wait for another condition, or ensure HttpTestingController
    mocks responses for all requests. Try adding HttpTestingController.verify()
    before your await fixture.whenStable to identify the open requests.
    Also, make sure your tests wait for the stability promise. We found many
    examples of tests that did not, meaning the expectations did not execute
    within the test body.

    In addition, ComponentFixture.isStable would synchronously switch to
    true in some scenarios but will now always be asynchronous.

  • Angular will ensure change detection runs, even when the state update originates from
    outside the zone, tests may observe additional rounds of change
    detection compared to the previous behavior.

    This change will be more likely to impact existing unit tests.
    This should usually be seen as more correct and the test should be updated,
    but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
    provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
    to the TestBed providers.

    Similarly, applications which may want to update state outside the zone
    and not trigger change detection can add
    provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
    to the providers in bootstrapApplication or add
    schedulingMode: NgZoneSchedulingMode.NgZoneOnly to the
    BootstrapOptions of bootstrapModule.

  • When Angular runs change detection, it will continue to
    refresh any views attached to ApplicationRef that are still marked for
    check after one round completes. In rare cases, this can result in infinite
    loops when certain patterns continue to mark views for check using
    ChangeDetectorRef.detectChanges. This will be surfaced as a runtime
    error with the NG0103 code.

  • async has been removed, use waitForAsync instead.

  • The ComponentFixture.autoDetect feature now executes
    change detection for the fixture within ApplicationRef.tick. This more
    closely matches the behavior of how a component would refresh in
    production. The order of component refresh in tests may be slightly
    affected as a result, especially when dealing with additional components
    attached to the application, such as dialogs. Tests sensitive to this
    type of change (such as screenshot tests) may need to be updated.
    Concretely, this change means that the component will refresh before
    additional views attached to ApplicationRef (i.e. dialog components).
    Prior to this change, the fixture component would refresh after other
    views attached to the application.

  • The exact timing of change detection execution when
    using event or run coalescing with NgZone is now the first of either
    setTimeout or requestAnimationFrame. Code which relies on this
    timing (usually by accident) will need to be adjusted. If a callback
    needs to execute after change detection, we recommend afterNextRender
    instead of something like setTimeout.

  • Newly created and views marked for check and reattached
    during change detection are now guaranteed to be refreshed in that same
    change detection cycle. Previously, if they were attached at a location
    in the view tree that was already checked, they would either throw
    ExpressionChangedAfterItHasBeenCheckedError or not be refreshed until
    some future round of change detection. In rare circumstances, this
    correction can cause issues. We identified one instance that relied on
    the previous behavior by reading a value on initialization which was
    queued to be updated in a microtask instead of being available in the
    current change detection round. The component only read this value during
    initialization and did not read it again after the microtask updated it.

  • Testability methods increasePendingRequestCount,
    decreasePendingRequestCount and getPendingRequestCount have been
    removed. This information is tracked with zones.

http
  • By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the includeRequestsWithAuthHeaders option in withHttpTransferCache.

    Example:

    withHttpTransferCache({
      includeRequestsWithAuthHeaders: true,
    })
platform-browser
  • Deprecated StateKey, TransferState and makeStateKey have been removed from @angular/platform-browser, use the same APIs from @angular/core.
platform-browser-dynamic
  • No longer used RESOURCE_CACHE_PROVIDER APIs have been removed.
platform-server
  • deprecated platformDynamicServer has been removed. Add an import @&#8203;angular/compiler and replace the usage with platformServer

  • deprecated ServerTransferStateModule has been removed. TransferState can be use without providing this module.

  • deprecated useAbsoluteUrl and baseUrl been removed from PlatformConfig. Provide and absolute url instead.

  • Legacy handling or Node.js URL parsing has been removed from ServerPlatformLocation.

    The main differences are;

    • pathname is always suffixed with a /.
    • port is empty when http: protocol and port in url is `8

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

Copy link
Contributor Author

renovate bot commented Jan 23, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @asymmetrik/ngx-leaflet@15.0.1
npm ERR! Found: @angular/common@17.0.9
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^17.0.8" from the root project
npm ERR!   peer @angular/common@"17.0.9" from @angular/forms@17.0.9
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"^17.0.8" from the root project
npm ERR!     peer @angular/forms@"^17.0.0" from primeng@17.2.0
npm ERR!     node_modules/primeng
npm ERR!       primeng@"17.2.0" from the root project
npm ERR!   8 more (@angular/platform-browser, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"15" from @asymmetrik/ngx-leaflet@15.0.1
npm ERR! node_modules/@asymmetrik/ngx-leaflet
npm ERR!   @asymmetrik/ngx-leaflet@"^15.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/common@15.2.10
npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@"15" from @asymmetrik/ngx-leaflet@15.0.1
npm ERR!   node_modules/@asymmetrik/ngx-leaflet
npm ERR!     @asymmetrik/ngx-leaflet@"^15.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-23T23_13_30_854Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-23T23_13_30_854Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch from 2aa30f5 to 6c1b54d Compare January 23, 2024 01:49
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch 2 times, most recently from 514a955 to a5b4f9b Compare January 31, 2024 15:17
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch from a5b4f9b to a87c8f7 Compare February 9, 2024 06:49
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch 7 times, most recently from b004a74 to c38f2f6 Compare February 24, 2024 17:00
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch 2 times, most recently from ee76e04 to c0ec5d3 Compare April 1, 2024 21:25
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch from c0ec5d3 to 9d811c1 Compare April 10, 2024 22:41
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch from 9d811c1 to f84b1b0 Compare April 23, 2024 23:13
@renovate renovate bot force-pushed the renovate/major-frontenddevdependencies branch from f84b1b0 to 05e0601 Compare May 22, 2024 21:28
Copy link
Contributor Author

renovate bot commented May 22, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: allerta-vvf@0.0.0
npm error Found: @angular/compiler@17.3.10
npm error node_modules/@angular/compiler
npm error   @angular/compiler@"^17.0.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler@"18.0.0" from @angular/compiler-cli@18.0.0
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"^18.0.0" from the root project
npm error   peer @angular/compiler-cli@"^18.0.0" from @angular-devkit/build-angular@18.0.0
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"^18.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-22T21_28_08_042Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T21_28_08_042Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants