@ms-cloudpack/cli 0.77.31 → 0.77.32
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.
- package/package.json +7 -7
- package/schema/AppConfig.json +1 -1
- package/schema/UserConfig.json +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ms-cloudpack/cli",
|
|
3
|
-
"version": "0.77.
|
|
3
|
+
"version": "0.77.32",
|
|
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",
|
|
@@ -30,18 +30,18 @@
|
|
|
30
30
|
"test": "cloudpack-scripts test"
|
|
31
31
|
},
|
|
32
32
|
"dependencies": {
|
|
33
|
-
"@ms-cloudpack/api-server": "^0.65.
|
|
34
|
-
"@ms-cloudpack/app-server": "^0.20.
|
|
35
|
-
"@ms-cloudpack/bundler": "^0.27.
|
|
33
|
+
"@ms-cloudpack/api-server": "^0.65.13",
|
|
34
|
+
"@ms-cloudpack/app-server": "^0.20.37",
|
|
35
|
+
"@ms-cloudpack/bundler": "^0.27.3",
|
|
36
36
|
"@ms-cloudpack/bundler-capabilities": "^0.5.0",
|
|
37
37
|
"@ms-cloudpack/common-types": "^0.33.1",
|
|
38
|
-
"@ms-cloudpack/config": "^0.38.
|
|
38
|
+
"@ms-cloudpack/config": "^0.38.22",
|
|
39
39
|
"@ms-cloudpack/create-express-app": "^1.10.66",
|
|
40
40
|
"@ms-cloudpack/environment": "^0.1.1",
|
|
41
41
|
"@ms-cloudpack/file-watcher": "^0.4.24",
|
|
42
42
|
"@ms-cloudpack/json-utilities": "^0.1.11",
|
|
43
|
-
"@ms-cloudpack/link-proxy": "^0.2.
|
|
44
|
-
"@ms-cloudpack/overlay": "^0.19.
|
|
43
|
+
"@ms-cloudpack/link-proxy": "^0.2.59",
|
|
44
|
+
"@ms-cloudpack/overlay": "^0.19.55",
|
|
45
45
|
"@ms-cloudpack/package-utilities": "^13.2.5",
|
|
46
46
|
"@ms-cloudpack/path-string-parsing": "^1.2.7",
|
|
47
47
|
"@ms-cloudpack/path-utilities": "^3.2.2",
|
package/schema/AppConfig.json
CHANGED
|
@@ -1917,7 +1917,7 @@
|
|
|
1917
1917
|
"items": {
|
|
1918
1918
|
"type": "string"
|
|
1919
1919
|
},
|
|
1920
|
-
"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
|
|
1920
|
+
"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 - Valid: `{configDir}/store`, `{configDir}/components` - Invalid: `some/path/{configDir}` or `{configDir}/{configDir}/nested`"
|
|
1921
1921
|
},
|
|
1922
1922
|
"dedupe": {
|
|
1923
1923
|
"type": "array",
|
package/schema/UserConfig.json
CHANGED
|
@@ -1918,7 +1918,7 @@
|
|
|
1918
1918
|
"items": {
|
|
1919
1919
|
"type": "string"
|
|
1920
1920
|
},
|
|
1921
|
-
"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
|
|
1921
|
+
"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 - Valid: `{configDir}/store`, `{configDir}/components` - Invalid: `some/path/{configDir}` or `{configDir}/{configDir}/nested`"
|
|
1922
1922
|
},
|
|
1923
1923
|
"dedupe": {
|
|
1924
1924
|
"type": "array",
|