Skip to main content
skill CX Codex

webflow-code-component:troubleshoot-deploy — Claude Code skill

Walks through failed Webflow Code Components deploys: reads the error, finds the root cause, hands you a specific fix.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add webflow/webflow-skills --skill webflow-code-component:troubleshoot-deploy -a claude-code
npx skills add webflow/webflow-skills --skill troubleshoot-deploy -a claude-code
Open on GitHub

What webflow-code-component:troubleshoot-deploy does

The skill kicks in when npx webflow library share fails or components deploy but misbehave. It asks for the exact error text and command output, checks whether this is a first deploy or an update, then sorts the failure into a category: auth, build, bundle size, network, config.

A reference catalog covers the usual suspects. "Authentication failed" means regenerating the token in Workspace Settings and re-exporting WEBFLOW_WORKSPACE_API_TOKEN. "Module not found" points at a missing @webflow/react. Missing styles usually mean CSS was never imported in the .webflow.tsx file. SSR gets its own section: wrap browser APIs in useEffect or turn SSR off with declareComponent.

You need Node.js 18+, React 18+, TypeScript and @webflow/webflow-cli for any of this to run. When nothing in the catalog matches, the skill gathers escalation data instead: npx webflow library log, a --verbose deploy, your Node.js version, the contents of webflow.json. Worth checking that config before you file a support ticket.

What it helps with

  • decode an error from webflow library share
  • recover from an expired API token
  • track down TypeScript errors before deploying
  • shrink a bundle that exceeds the size limit
  • collect logs for a Webflow support ticket

Example prompts for the agent

  • My deploy failed with Authentication failed, how do I fix it?
  • Here's the output of npx webflow library share --verbose, find the cause
  • Components deployed but the styles are missing — why?

How to install webflow-code-component:troubleshoot-deploy

1Skills CLI (Vercel)

npx skills add webflow/webflow-skills --skill webflow-code-component:troubleshoot-deploy -a claude-code
npx skills add webflow/webflow-skills --skill troubleshoot-deploy -a claude-code

2Manually: put the files in place

~/.claude/skills/troubleshoot-deploy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/troubleshoot-deploy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about webflow-code-component:troubleshoot-deploy

How do I install webflow-code-component:troubleshoot-deploy in Claude?

Run npx skills add webflow/webflow-skills --skill webflow-code-component:troubleshoot-deploy -a claude-code. The skill lands at ~/.claude/skills/troubleshoot-deploy/SKILL.md.

What does this skill do?

It debugs failed Webflow Code Components deploys: identifies the error category, explains the root cause and gives step-by-step fixes with a way to verify each one.

What do I need for it to work?

Node.js 18+, React 18+, TypeScript and the @webflow/webflow-cli package. Without them the deploy and type-check commands won't run.

Source text

SKILL.md · MIT
---
name: webflow-code-component:troubleshoot-deploy
description: Debug deployment failures for Webflow Code Components. Analyzes error messages, identifies root causes, and provides specific fixes for common issues.
compatibility: Node.js 18+, React 18+, TypeScript, @webflow/webflow-cli
metadata:
  author: webflow
  version: "1.1"
---

# Troubleshoot Deploy

Debug and fix deployment issues for Webflow Code Components.

## When to Use This Skill

**Use when:**
- `webflow library share` failed with an error
- Components deployed but aren't working correctly
- User shares an error message from deployment
- Bundle or compilation errors occurred

**Do NOT use when:**
- Deployment hasn't been attempted yet (use deploy-guide instead)
- Validating before deployment (use pre-deploy-check instead)
- General code quality issues (use component-audit instead)

## Instructions

### Phase 1: Gather Information

1. **Get error details**:
   - Ask for exact error message
   - Request output from `npx webflow library share`
   - Check if `npx webflow library log` has additional info

2. **Understand context**:
   - First deploy or update?
   - Recent changes made?
   - Working previously?

### Phase 2: Diagnose

3. **Identify error category**:
   - Authentication errors
   - Build/compilation errors
   - Bundle size errors
   - Network/upload errors
   - Configuration errors

4. **Analyze root cause**:
   - Parse error message
   - Check common causes
   - Identify specific issue

### Phase 3: Provide Solution

5. **Give specific fix**:
   - Step-by-step resolution
   - Code examples if needed
   - Verification steps

6. **Prevent recurrence**:
   - Explain why it happened
   - Suggest preventive measures

## Common Error Reference

For detailed solutions to each error, see [references/ERROR_CATALOG.md](references/ERROR_CATALOG.md).

### Quick Reference

| Error | Category | Quick Fix |
|-------|----------|-----------|
| "Authentication failed" | Auth | Regenerate API token in Workspace Settings |
| "Insufficient permissions" | Auth | Check workspace role and token |
| "Module not found" | Build | `npm install --save-dev @webflow/react` |
| "TypeScript errors" | Build | Run `npx tsc --noEmit` to find error |
| "Unexpected token" | Build | Check file extension is `.tsx` |
| "Bundle size exceeds limit" | Bundle | Tree-shake imports, lazy load heavy components |
| "Component not rendering" | Runtime | Check SSR issues, browser console |
| "Styles not appearing" | Runtime | Import CSS in .webflow.tsx file |
| "webflow.json not found" | Config | Create webflow.json in project root |
| "No components found" | Config | Check glob pattern and file extension |
| "Invalid JSON in webflow.json" | Config | Fix JSON syntax (trailing commas, comments) |
| "429 Too Many Requests" | Network | Wait 60 seconds and retry |
| "Request timed out" | Network | Check connectivity, proxy, Webflow status |
| "JavaScript heap out of memory" | Memory | `NODE_OPTIONS="--max-old-space-size=4096"` |
| "Circular dependency" | Build | Extract shared code, break import cycles |

### Most Common Fixes

**Authentication:**
```bash
# Regenerate token, then:
export WEBFLOW_WORKSPACE_API_TOKEN=your-new-token
npx webflow library share
```

**Missing Dependencies:**
```bash
npm install --save-dev @webflow/webflow-cli @webflow/data-types @webflow/react
```

**SSR Issues:**
```typescript
// Wrap browser APIs in useEffect or disable SSR:
declareComponent(Component, { options: { ssr: false } });
```

**Missing Styles:**
```typescript
// In .webflow.tsx, import styles:
import "./Component.module.css";
```

## Debugging Commands

```bash
# Check recent deploy logs
npx webflow library log

# Verbose deploy output (shows detailed errors)
npx webflow library share --verbose

# Type check without deploying
npx tsc --noEmit
```

## Validation

The issue is resolved when all of the following are true:

| Success Criteria | How to Verify |
|-----------------|---------------|
| Deploy completes without errors | `npx webflow library share` exits cleanly |
| Components appear in Designer | Open Add panel in Designer and find your library |
| Import logs confirm success | `npx webflow library log` shows successful import |

## Guidelines

### Error Analysis Process

1. **Read the full error message** - Often contains the solution
2. **Check the error category** - Auth, build, bundle, or runtime
3. **Look for file paths** - Points to exact location
4. **Check line numbers** - For code errors
5. **Search error message** - May be a known issue

### When to Escalate

If none of the solutions work, gather this data before escalating:

1. **Deploy logs**: `npx webflow library log`
2. **Verbose output**: `npx webflow library share --verbose`
3. **Node.js version**: `node -v`
4. **Package versions**: `npm list @webflow/webflow-cli @webflow/data-types @webflow/react`
5. **Configuration**: Contents of `webflow.json`
6. **Error message**: Full error output (not just the summary line)

Then:
- Check **Webflow status page** for outages
- Search the **Webflow Community Forum** for your error message
- Contact **Webflow Support** with the collected data above

© webflow · MIT · webflow/webflow-skills

Similar skills

Everything for Frontend and UI →

From the same set21

webflow-cli:devlink Pulls Webflow Designer components into React and Next.js code, syncs later design edits, and shows what changed after each sync. CX Codex +1 998installs webflow-code-component:convert-component Turns an existing React component into a Webflow Code Component: reads the props, writes the .webflow.tsx definition and flags what has to change. CX Codex +1 995installs webflow-code-component:pre-deploy-check Validates Webflow Code Components before you publish: bundle size, dependencies, props, SSR and styling. Useful right before webflow library share. CX Codex +1 988installs webflow-code-component:deploy-guide A skill that walks you through publishing a code component library to a Webflow workspace, from pre-flight checks to verifying components in Designer. CX Codex +1 987installs webflow-mcp:accessibility-audit Audits Webflow pages against WCAG 2.1 accessibility criteria and applies fixes directly via MCP tools without opening the Webflow Designer. CX Codex +1 887installs webflow-mcp:cms-best-practices A skill that walks your agent through Webflow CMS architecture: collection planning, field types, relationships and troubleshooting. CX Codex +1 877installs webflow-mcp:site-audit This skill walks a Webflow site and builds an inventory of pages, CMS collections and fields, then returns a report with a content health score. CX Codex +1 862installs webflow-mcp:link-checker Finds and fixes broken, insecure, or redirecting links across Webflow static pages and CMS collections. Useful for pre-launch link validation and routine SEO audits. CX Codex +1 851installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor