ip-address VS Angular

{ "_from": "[email protected]", "_id": "[email protected]", "_inBundle": false, "_integrity": "sha512-dHkI3/YNJq4b/qQaz+c8LuarD3pY24JqZWfjB8aZx1gtpc2MDILu9L9jpZe1sHpzo/yWFweQVn+U//FhazUxmw==", "_location": "/ip-address", "_phantomChildren": {}, "_requested": { "type": "range", "registry": true, "raw": "[email protected]", "name": "ip-address", "escapedName": "ip-address", "rawSpec": "5.8.9", "saveSpec": null, "fetchSpec": "5.8.9" }, "_requiredBy": [ "/geoip-lite" ], "_resolved": "https://registry.npmjs.org/ip-address/-/ip-address-5.9.4.tgz", "_shasum": "4660ac261ad61bd397a860a007f7e98e4eaee386", "_spec": "[email protected]", "_where": "E:\git_6_cycle2\git\client\kanomi_apps\Weather\zip\node_modules\geoip-lite", "author": { "name": "Beau Gunderson", "email": "[email protected]", "url": "https://beaugunderson.com/" }, "bugs": { "url": "https://github.com/beaugunderson/ip-address/issues" }, "bundleDependencies": false, "dependencies": { "jsbn": "1.1.0", "lodash": "4.17.15", "sprintf-js": "1.1.2" }, "deprecated": false, "description": "A library for parsing IPv4 and IPv6 IP addresses in node and the browser.", "devDependencies": { "browserify": "16.3.0", "chai": "4.2.0", "codecov.io": "0.1.6", "documentation": "12.0.3", "istanbul": "0.4.5", "mocha": "6.2.0", "mochify": "6.3.0" }, "engines": { "node": ">= 0.10" }, "homepage": "https://github.com/beaugunderson/ip-address#readme", "keywords": [ "ipv6", "ipv4", "browser", "validation" ], "license": "MIT", "main": "ip-address.js", "name": "ip-address", "repository": { "type": "git", "url": "git://github.com/beaugunderson/ip-address.git" }, "scripts": { "docs": "documentation build --github --output docs --format html ./ip-address.js", "prepublishOnly": "browserify ./ip-address-globals.js > ./dist/ip-address-globals.js", "test": "mocha -R spec" }, "version": "5.9.4" }

/** * https://github.com/angular/angular/blob/75a186e321cb417685b2f13e9961906fc0aed36c/packages/core/src/render3/reactivity/untracked.ts#L15 * * packages/core/src/render3/reactivity/untracked.ts * **/ export function untracked(nonReactiveReadsFn: () => T): T { const prevConsumer = setActiveConsumer(null); try { return nonReactiveReadsFn(); } finally { setActiveConsumer(prevConsumer); } }

source: https://github.com/angular/angular/issues/46542

Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.

In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:

For scheduling, I use awesome code I found in the Angular source code.

Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please 🙏)️.

Link — angular/CONTRIBUTING.md

Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.