@ms-cloudpack/common-types - npm Package Compare versions

Comparing version 0.28.1 to 0.28.2

lib/AppConfig.d.ts

@@ -8,2 +8,3 @@ import type { ServerConfig } from './ServerConfig.js';
 import type { DefineFlags } from '@ms-cloudpack/common-types-browser';
+import type { ModuleResolutionConfig } from './ModuleResolutionConfig.js';
 /**
@@ -105,3 +106,7 @@ * Per-application user-provided configuration for Cloudpack.
     defaultBundler?: string;
+    /**
+     * Configuration for module resolution, specifying where to look for modules.
+     */
+    resolve?: ModuleResolutionConfig;
 }
 //# sourceMappingURL=AppConfig.d.ts.map

lib/index.d.ts

@@ -42,2 +42,3 @@ export { allFeatures, defaultFeatures, type Features, type FeatureName } from './allFeatures.js';
 export type { WithRequired } from './WithRequired.js';
+export type { ModuleResolutionConfig } from './ModuleResolutionConfig.js';
 //# sourceMappingURL=index.d.ts.map

package.json

 {
   "name": "@ms-cloudpack/common-types",
-  "version": "0.28.1",
+  "version": "0.28.2",
   "description": "Common types for Cloudpack.",
@@ -5,0 +5,0 @@ "license": "MIT",

schema/AppConfig.json

@@ -105,2 +105,6 @@ {
     },
+    "resolve": {
+      "$ref": "#/definitions/ModuleResolutionConfig",
+      "description": "Configuration for module resolution, specifying where to look for modules."
+    },
     "$schema": {
@@ -1275,4 +1279,17 @@ "type": "string"
       "description": "DefineFlags is an interface that represents a collection of global variables that will be defined on the window object. Each define flag is represented by a key-value pair"
+    },
+    "ModuleResolutionConfig": {
+      "type": "object",
+      "properties": {
+        "modules": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "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\""
+        }
+      },
+      "additionalProperties": false
     }
   }
 }

schema/UserConfig.json

@@ -108,2 +108,6 @@ {
           "default": "ori"
+        },
+        "resolve": {
+          "$ref": "#/definitions/ModuleResolutionConfig",
+          "description": "Configuration for module resolution, specifying where to look for modules."
         }
@@ -1276,2 +1280,15 @@ },
       "description": "DefineFlags is an interface that represents a collection of global variables that will be defined on the window object. Each define flag is represented by a key-value pair"
+    },
+    "ModuleResolutionConfig": {
+      "type": "object",
+      "properties": {
+        "modules": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "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\""
+        }
+      },
+      "additionalProperties": false
     }
@@ -1278,0 +1295,0 @@ },

No alert changes

Improved metrics

Total package byte prevSize

327460

2.19%

Number of package files

174

2.35%

Lines of code

4723

1.57%

No dependency changes