supbuddy 3.0.9 → 3.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -48250,7 +48250,7 @@ port ${port}
48250
48250
  commands.push(`cp "${tmpPath}" "${filePath}"`);
48251
48251
  }
48252
48252
  const writeChain = commands.join(" && ");
48253
- const flush = "{ dscacheutil -flushcache; killall -HUP mDNSResponder 2>/dev/null; true; }";
48253
+ const flush = "{ dscacheutil -flushcache; launchctl kickstart -k system/com.apple.mDNSResponder.reloaded 2>/dev/null || launchctl kickstart -k system/com.apple.mDNSResponder 2>/dev/null || killall -HUP mDNSResponder 2>/dev/null; true; }";
48254
48254
  return { command: `${writeChain} && ${flush}`, tmpFiles };
48255
48255
  }
48256
48256
  async function buildMacOsCleanupCommand() {
@@ -50019,7 +50019,7 @@ async function checkProxyReachabilityAndSurface() {
50019
50019
  const hintMessage = {
50020
50020
  mdns_hijack: `Browser DNS for ${result.domain} returns ${result.resolved.join(", ")} (your own LAN IP) but Caddy isn't reachable on port ${result.port}. This usually means LAN sharing is publishing the name via Bonjour and pf rules need a re-apply — toggle the proxy off/on, or disable LAN sharing.`,
50021
50021
  foreign_owner: `Another device on your LAN is responding for ${result.domain} (${result.resolved.join(", ")}) — Bonjour/mDNS race for the .local namespace. Switch this project's TLD to .test in Settings, or take the other device offline.`,
50022
- no_resolution: `The OS resolver couldn't resolve ${result.domain}. Check that /etc/resolver/<project-domain> exists (visible in get_health dns.resolver) and that the DNS server on :${store2.dnsState.port} is answering.`,
50022
+ no_resolution: `The OS resolver couldn't resolve ${result.domain}. The resolver files and DNS server on :${store2.dnsState.port} may be fine — on macOS Sonoma+ the OS often just hasn't loaded /etc/resolver yet. Click RETRY (or restart the proxy) to rewrite the resolver files and reload the OS DNS cache. If it persists, run get_health → dns.resolver to check for missing files.`,
50023
50023
  resolved_but_unreachable: `${result.domain} resolves to ${result.resolved.join(", ")} but TCP connect to port ${result.port} fails. Likely a port-forwarding rule is missing for that IP — toggle the proxy off/on.`
50024
50024
  };
50025
50025
  const effectiveHint = resolveReachabilityHint2(result.hint, store2.settings.lanSharing);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "supbuddy",
3
- "version": "3.0.9",
3
+ "version": "3.0.10",
4
4
  "description": "Run multiple Supabase projects at once on custom local domains with HTTPS. A headless CLI and daemon (proxy, DNS, Supabase/Compose lifecycle, MCP) for macOS and Linux.",
5
5
  "keywords": [
6
6
  "supabase",