framer-debug-bundle

name	framer-debug-bundle
description	Collect Framer debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Framer problems. Trigger with phrases like "framer debug", "framer support bundle", "collect framer logs", "framer diagnostic".
allowed-tools	Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version	1.5.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","framer"]
compatibility	Designed for Claude Code

Framer Debug Bundle

Overview

Collect diagnostic information for Framer plugin or Server API issues including package versions, API connectivity, and configuration.

Instructions

Step 1: Create Debug Bundle

#!/bin/bash
BUNDLE="framer-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"

echo "=== Framer Debug Bundle ===" | tee "$BUNDLE/summary.txt"
echo "Date: $(date -u)" >> "$BUNDLE/summary.txt"

# Runtime
echo "--- Runtime ---" >> "$BUNDLE/summary.txt"
node --version >> "$BUNDLE/summary.txt" 2>&1
npm --version >> "$BUNDLE/summary.txt" 2>&1

# Packages
echo "--- Packages ---" >> "$BUNDLE/summary.txt"
npm list framer-plugin framer-api framer 2>/dev/null >> "$BUNDLE/summary.txt"

# Credentials (presence only)
echo "--- Config ---" >> "$BUNDLE/summary.txt"
echo "FRAMER_API_KEY: ${FRAMER_API_KEY:+[SET]}" >> "$BUNDLE/summary.txt"
echo "FRAMER_SITE_ID: ${FRAMER_SITE_ID:+[SET]}" >> "/summary.txt"


  >> 
curl -s -o /dev/null -w  https://api.framer.com/health >>  2>&1


 vite.config.ts  2>/dev/null
 tsconfig.json  2>/dev/null
 package.json  2>/dev/null


tar -czf