@nx/angular 19.2.1 → 19.2.2
Sign up to get free protection for your applications and to get access to all the features.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@nx/angular",
|
|
3
|
-
"version": "19.2.
|
|
3
|
+
"version": "19.2.2",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "The Nx Plugin for Angular contains executors, generators, and utilities for managing Angular applications and libraries within an Nx workspace. It provides: \n\n- Integration with libraries such as Storybook, Jest, ESLint, Tailwind CSS, Playwright and Cypress. \n\n- Generators to help scaffold code quickly (like: Micro Frontends, Libraries, both internal to your codebase and publishable to npm) \n\n- Single Component Application Modules (SCAMs) \n\n- NgRx helpers. \n\n- Utilities for automatic workspace refactoring.",
|
|
6
6
|
"repository": {
|
|
@@ -79,14 +79,14 @@
|
|
|
79
79
|
"tslib": "^2.3.0",
|
|
80
80
|
"webpack": "^5.80.0",
|
|
81
81
|
"webpack-merge": "^5.8.0",
|
|
82
|
-
"@nx/devkit": "19.2.
|
|
83
|
-
"@nx/js": "19.2.
|
|
84
|
-
"@nx/eslint": "19.2.
|
|
85
|
-
"@nx/webpack": "19.2.
|
|
86
|
-
"@nx/web": "19.2.
|
|
87
|
-
"@nx/workspace": "19.2.
|
|
82
|
+
"@nx/devkit": "19.2.2",
|
|
83
|
+
"@nx/js": "19.2.2",
|
|
84
|
+
"@nx/eslint": "19.2.2",
|
|
85
|
+
"@nx/webpack": "19.2.2",
|
|
86
|
+
"@nx/web": "19.2.2",
|
|
87
|
+
"@nx/workspace": "19.2.2",
|
|
88
88
|
"piscina": "^4.4.0",
|
|
89
|
-
"@nrwl/angular": "19.2.
|
|
89
|
+
"@nrwl/angular": "19.2.2"
|
|
90
90
|
},
|
|
91
91
|
"peerDependencies": {
|
|
92
92
|
"@angular-devkit/build-angular": ">= 16.0.0 < 19.0.0",
|
|
@@ -139,7 +139,7 @@
|
|
|
139
139
|
"items": {
|
|
140
140
|
"type": "string"
|
|
141
141
|
},
|
|
142
|
-
"description": "List of remote applications to not automatically serve, either statically or in development mode. This will not remove the remotes from the `module-federation.config` file, and therefore the application may still try to fetch these remotes.\nThis option is useful
|
|
142
|
+
"description": "List of remote applications to not automatically serve, either statically or in development mode. This will not remove the remotes from the `module-federation.config` file, and therefore the application may still try to fetch these remotes.\nThis option is useful if you have other means for serving the `remote` application(s).\n**NOTE:** Remotes that are not in the workspace will be skipped automatically."
|
|
143
143
|
},
|
|
144
144
|
"pathToManifestFile": {
|
|
145
145
|
"type": "string",
|