fix(cli): mud set-version --link shouldn't fetch versions (#2000)

Co-authored-by: Kevin Ingersoll <kingersoll@gmail.com>
latticexyz · Dec 4, 2023 · 854de07 · 854de07
1 parent 809905d
commit 854de07
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 1 deletion.
diff --git a/.changeset/clean-bananas-hug.md b/.changeset/clean-bananas-hug.md
@@ -0,0 +1,5 @@
+---
+"@latticexyz/cli": patch
+---
+
+Using `mud set-version --link` will no longer attempt to fetch the latest version from npm.
diff --git a/packages/cli/src/commands/set-version.ts b/packages/cli/src/commands/set-version.ts
@@ -56,8 +56,11 @@ const commandModule: CommandModule<Options, Options> = {
         throw new MUDError(`These options are mutually exclusive: ${mutuallyExclusiveOptions.join(", ")}`);
       }
 
+      // If the --link flag is not set, we call resolveVersion to get the version
       // Resolve the version number from available options like `tag` or `commit`
-      options.mudVersion = await resolveVersion(options);
+      if (!options.link) {
+        options.mudVersion = await resolveVersion(options);
+      }
 
       // Update all package.json below the current working directory (except in node_modules)
       const packageJsons = glob.sync("**/package.json").filter((p) => !p.includes("node_modules"));