fix: pnpm failure on create-astro (#7435)

* fix: use which-pm-runs instead of preferred-pm

* deps: remove preferred-pm

* chore: move which-pm-runs to regular deps

* chore: changeset

.changeset/clever-rings-draw.md

@@ -0,0 +1,5 @@
+---
+'create-astro': patch
+---
+
+Fix registry failures using unexpected package managers when running create-astro

packages/create-astro/package.json

@@ -36,15 +36,14 @@
     "execa": "^6.1.0",
     "giget": "1.0.0",
     "mocha": "^9.2.2",
-    "preferred-pm": "^3.0.3"
+    "which-pm-runs": "^1.1.0"
   },
   "devDependencies": {
     "@types/which-pm-runs": "^1.0.0",
     "arg": "^5.0.2",
     "astro-scripts": "workspace:*",
     "strip-ansi": "^7.1.0",
-    "strip-json-comments": "^5.0.0",
-    "which-pm-runs": "^1.1.0"
+    "strip-json-comments": "^5.0.0"
   },
   "engines": {
     "node": ">=16.12.0"

packages/create-astro/src/messages.ts

@@ -4,15 +4,15 @@ import { align, sleep } from '@astrojs/cli-kit/utils';
 import { execa } from 'execa';
 import { exec } from 'node:child_process';
 import { get } from 'node:https';
-import preferredPM from 'preferred-pm';
 import stripAnsi from 'strip-ansi';
+import detectPackageManager from 'which-pm-runs';
 
 // Users might lack access to the global npm registry, this function
 // checks the user's project type and will return the proper npm registry
 //
 // A copy of this function also exists in the astro package
 async function getRegistry(): Promise<string> {
-	const packageManager = (await preferredPM(process.cwd()))?.name || 'npm';
+	const packageManager = detectPackageManager()?.name || 'npm';
 	const { stdout } = await execa(packageManager, ['config', 'get', 'registry']);
 	return stdout || 'https://registry.npmjs.org';
 }