fix: handle newer npm publish directories

4Catalyzer · Aug 19, 2022 · 961b8ac · 961b8ac
1 parent 35ac9d2
commit 961b8ac
Showing 1 changed file with 6 additions and 4 deletions.
diff --git a/packages/rollout/command.js b/packages/rollout/command.js
@@ -122,6 +122,12 @@ async function npmPublish(pkgJson, options) {
   const args = ['publish'];
 
   if (publishDir) {
+    // npm@7 and above require an unambigious path otherwise
+    // it will assume things like 'lib' or 'dist/esm' are github repos
+    if (!publishDir.startsWith('.') && !path.isAbsolute(publishDir)) {
+      publishDir = `./${publishDir}`
+    }
+
     args.push(publishDir, '--ignore-scripts');
 
     // We run the lifecycle scripts manually to ensure they run in
@@ -249,10 +255,6 @@ const handlerImpl = async (argv) => {
   // older rollout
   if (!publishDir && packageJson.release) {
     publishDir = packageJson.release.publishDir;
-    if (publishDir)
-      ConsoleUtilities.warn(
-        'publishDir in package.json `release` field is deprecated. Use the `publishConfig.directory` field instead.',
-      );
   }
 
   await runTasks([