You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:8703) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
When you visit http://localhost:4200/api.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
(node:8703) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 17.3.2
Node: 22.0.0 (Unsupported)
Package Manager: npm 10.5.1
OS: linux x64
Angular: 17.3.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1703.2
@angular-devkit/build-angular 17.3.2
@angular-devkit/core 17.3.2
@angular-devkit/schematics 17.3.2
@schematics/angular 17.3.2
rxjs 7.8.1
typescript 5.4.3
zone.js 0.14.4
Anything else?
I realize Angular doesn't support Node 22.0.0 yet, but I figure this may be a help on the right track to fix some future issues if someone likes. I'll use a supported Node in the meantime.
The text was updated successfully, but these errors were encountered:
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Overview
Node's DEP0060 when using proxy config and entering a URL target.
Details
After using a proxy (set with options in
@angular-devkit/build-anger:dev-server
):Inside
proxy.conf.json
using a simple proxy config:Will result in:
When you visit
http://localhost:4200/api
.Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Anything else?
I realize Angular doesn't support Node 22.0.0 yet, but I figure this may be a help on the right track to fix some future issues if someone likes. I'll use a supported Node in the meantime.
The text was updated successfully, but these errors were encountered: