feat: add the infrastructure to support "system" packages (#2085)

This enables `mason.nvim` to start managing certain packages that:

1) are not suitable for the core registry
2) should not surface in existing APIs and UIs

1 files changed, 17 insertions, 0 deletions

diff --git a/README.md b/README.md
index c233bee0..6c2a3ead 100644
--- a/README.md
+++ b/README.md
@@ -207,6 +207,14 @@ local DEFAULT_SETTINGS = {
         "github:mason-org/mason-registry",
     },
 
+    ---@since 2.3.0
+    -- [Advanced setting]
+    -- The registries to source system packages from. Accepts multiple entries. Should a package with the same name exist in
+    -- multiple registries, the registry listed first will be used.
+    system_registries = {
+        "github:mason-org/mason-system-registry",
+    },
+
     ---@since 1.0.0
     -- The provider implementations to use for resolving supplementary package metadata (e.g., all available versions).
     -- Accepts multiple entries, where later entries will be used as fallback should prior providers fail.
@@ -241,6 +249,15 @@ local DEFAULT_SETTINGS = {
         install_args = {},
     },
 
+    npm = {
+        ---@since 2.3.0
+        -- These args will be added to `npm install` calls. Note that setting extra args might impact intended behavior
+        -- and is not recommended.
+        --
+        -- Example: { "--registry", "https://registry.npmjs.org/" }
+        install_args = {},
+    },
+
     ui = {
         ---@since 1.0.0
         -- Whether to automatically check for new versions when opening the :Mason window.