@ms-cloudpack/cli 0.77.18 → 0.77.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +17 -17
  2. package/schema/AppConfig.json +7 -0
  3. package/schema/UserConfig.json +7 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ms-cloudpack/cli",
3
- "version": "0.77.18",
3
+ "version": "0.77.19",
4
4
  "description": "The Cloudpack command line interface - a tool for managing fast inner and outer looping in web apps.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -18,25 +18,25 @@
18
18
  "cloudpack": "./bin/cloudpack.js"
19
19
  },
20
20
  "dependencies": {
21
- "@ms-cloudpack/api-server": "^0.65.0",
22
- "@ms-cloudpack/app-server": "^0.20.24",
23
- "@ms-cloudpack/bundler": "^0.26.9",
24
- "@ms-cloudpack/bundler-capabilities": "^0.4.3",
25
- "@ms-cloudpack/common-types": "^0.31.0",
26
- "@ms-cloudpack/config": "^0.38.13",
27
- "@ms-cloudpack/create-express-app": "^1.10.58",
21
+ "@ms-cloudpack/api-server": "^0.65.1",
22
+ "@ms-cloudpack/app-server": "^0.20.25",
23
+ "@ms-cloudpack/bundler": "^0.26.10",
24
+ "@ms-cloudpack/bundler-capabilities": "^0.4.4",
25
+ "@ms-cloudpack/common-types": "^0.31.1",
26
+ "@ms-cloudpack/config": "^0.38.14",
27
+ "@ms-cloudpack/create-express-app": "^1.10.59",
28
28
  "@ms-cloudpack/environment": "^0.1.1",
29
- "@ms-cloudpack/file-watcher": "^0.4.16",
29
+ "@ms-cloudpack/file-watcher": "^0.4.17",
30
30
  "@ms-cloudpack/json-utilities": "^0.1.11",
31
- "@ms-cloudpack/link-proxy": "^0.2.46",
32
- "@ms-cloudpack/overlay": "^0.19.42",
33
- "@ms-cloudpack/package-utilities": "^13.1.3",
31
+ "@ms-cloudpack/link-proxy": "^0.2.47",
32
+ "@ms-cloudpack/overlay": "^0.19.43",
33
+ "@ms-cloudpack/package-utilities": "^13.1.4",
34
34
  "@ms-cloudpack/path-string-parsing": "^1.2.7",
35
- "@ms-cloudpack/path-utilities": "^3.1.29",
36
- "@ms-cloudpack/remote-cache": "^0.11.49",
37
- "@ms-cloudpack/setup-utilities": "^0.5.50",
35
+ "@ms-cloudpack/path-utilities": "^3.1.30",
36
+ "@ms-cloudpack/remote-cache": "^0.11.50",
37
+ "@ms-cloudpack/setup-utilities": "^0.5.51",
38
38
  "@ms-cloudpack/task-reporter": "^0.17.4",
39
- "@ms-cloudpack/telemetry": "^0.11.49",
39
+ "@ms-cloudpack/telemetry": "^0.11.50",
40
40
  "@yarnpkg/lockfile": "^1.1.0",
41
41
  "commander": "^14.0.0",
42
42
  "cross-spawn": "^7.0.3",
@@ -49,7 +49,7 @@
49
49
  "workspace-tools": "^0.38.0"
50
50
  },
51
51
  "devDependencies": {
52
- "@ms-cloudpack/common-types": "^0.31.0",
52
+ "@ms-cloudpack/common-types": "^0.31.1",
53
53
  "@ms-cloudpack/common-types-browser": "^0.6.3",
54
54
  "@ms-cloudpack/eslint-plugin-internal": "^0.0.1",
55
55
  "@ms-cloudpack/scripts": "^0.0.1",
package/schema/AppConfig.json CHANGED
@@ -1343,6 +1343,13 @@
1343
1343
  "type": "string"
1344
1344
  },
1345
1345
  "description": "Folder names or directory paths where to find modules.\n\n**Note: This completely replaces the default node_modules lookup. To keep node_modules, include it explicitly: [\"node_modules\", \"{configDir}/store\"]**\n\nAbsolute and relative paths can both be used, but be aware that they will behave a bit differently.\n\nA relative path will be scanned similarly to how Node scans for node_modules, by looking through the current directory as well as its ancestors (i.e. ./node_modules, ../node_modules, and on).\n\nWith an absolute path, it will only search in the given directory.\n\nTemplate variables:\n- {configDir} can be used to build paths relative to the configuration directory. For example: {configDir}/store resolves to an absolute path pointing to the 'store' subdirectory within the directory containing the configuration file.\n\n Restrictions: - The {configDir} template must appear at the beginning of the path - Only one {configDir} template is allowed per path - Invalid: \"some/path/{configDir}\" or \"{configDir}/{configDir}/nested\" - Valid: \"{configDir}/store\", \"{configDir}/components\""
1346
+ },
1347
+ "dedupe": {
1348
+ "type": "array",
1349
+ "items": {
1350
+ "type": "string"
1351
+ },
1352
+ "description": "Array of module names to enforce consistent resolution using the application's module resolution strategy.\n\nPrevents multiple instances of the same package when dealing with duplicate dependencies that may arise from package hoisting or linked dependencies in monorepo setups.\n\nExample: [\"react\", \"lodash\"] ensures these packages are always resolved using the same resolution path that the application would normally use.\n\nThis settings will be ignored for inlinedDependencies."
1346
1353
  }
1347
1354
  },
1348
1355
  "additionalProperties": false
package/schema/UserConfig.json CHANGED
@@ -1344,6 +1344,13 @@
1344
1344
  "type": "string"
1345
1345
  },
1346
1346
  "description": "Folder names or directory paths where to find modules.\n\n**Note: This completely replaces the default node_modules lookup. To keep node_modules, include it explicitly: [\"node_modules\", \"{configDir}/store\"]**\n\nAbsolute and relative paths can both be used, but be aware that they will behave a bit differently.\n\nA relative path will be scanned similarly to how Node scans for node_modules, by looking through the current directory as well as its ancestors (i.e. ./node_modules, ../node_modules, and on).\n\nWith an absolute path, it will only search in the given directory.\n\nTemplate variables:\n- {configDir} can be used to build paths relative to the configuration directory. For example: {configDir}/store resolves to an absolute path pointing to the 'store' subdirectory within the directory containing the configuration file.\n\n Restrictions: - The {configDir} template must appear at the beginning of the path - Only one {configDir} template is allowed per path - Invalid: \"some/path/{configDir}\" or \"{configDir}/{configDir}/nested\" - Valid: \"{configDir}/store\", \"{configDir}/components\""
1347
+ },
1348
+ "dedupe": {
1349
+ "type": "array",
1350
+ "items": {
1351
+ "type": "string"
1352
+ },
1353
+ "description": "Array of module names to enforce consistent resolution using the application's module resolution strategy.\n\nPrevents multiple instances of the same package when dealing with duplicate dependencies that may arise from package hoisting or linked dependencies in monorepo setups.\n\nExample: [\"react\", \"lodash\"] ensures these packages are always resolved using the same resolution path that the application would normally use.\n\nThis settings will be ignored for inlinedDependencies."
1347
1354
  }
1348
1355
  },
1349
1356
  "additionalProperties": false