Skip to main content
Question

Recent Figma Make Update Blocks Editing Legitimate HTML Files - Plugin Hook Error

  • April 30, 2026
  • 2 replies
  • 32 views

TinyDancer

Issue: After a recent Figma Make update (approximately April 30, 2026), the application now blocks all attempts to edit .html files, incorrectly identifying them as incompatible with a "TypeScript + React application."

Error Message:

PreToolUse:Edit hook error: [${CLAUDE_PLUGIN_ROOT}/hooks/block-bad-file-extensions.js]: 
Blocked: This is a Typescript + React application. Please write to a TSX file instead.

Impact:

  • Cannot edit legitimate HTML files used for third-party platform integrations
  • Breaks existing workflow that has functioned correctly for months
  • Forces use of workarounds (command-line editing) instead of standard editing tools
  • Affects regular maintenance tasks

Technical Details:

What's Happening: The Figma Make plugin added a pre-tool-use hook (block-bad-file-extensions.js) that appears to assume all files in a Figma Make workspace should be React/TypeScript components. This hook blocks the Edit and Write tools from modifying .html files.

What I've Tried:

  1. ✅ Restarted Figma Make - no effect
  2. ✅ Created .claude/settings.json with explicit file permissions - hook still blocks
  3. ✅ Restarted after settings file creation - hook still blocks
  4. ❌ The plugin-level hook appears to override project-level settings

Current Workaround: Using bash command-line tools to bypass the hook, which works but is not ideal for regular workflow.

Expected Behavior:

Figma Make should:

  1. Allow editing of legitimate HTML files (not all HTML is React)
  2. Respect project-level settings that explicitly allow HTML file editing
  3. Only block file types that are genuinely incompatible with the project structure

Use Case Context:

I use Figma Make for a web application that integrates with third-party platforms. This requires maintaining custom HTML/CSS/JS files for integration purposes. These are legitimate HTML files for web hosting, not React components.

This workflow has functioned perfectly for months until this recent update.

Suggested Fix:

  1. Update the block-bad-file-extensions.js hook to:

    • Exclude HTML files from blanket blocking, OR
    • Intelligently detect whether HTML files are part of a React structure or standalone web files, OR
    • Allow project-level settings (.claude/settings.json) to override the hook
  2. Make the hook more intelligent about detecting actual React projects vs. workspaces that contain HTML for other purposes

Request:

Please investigate and fix this hook behavior in a future Figma Make update. The hook is preventing legitimate use of HTML files for non-React purposes.

Temporary workaround is available but not sustainable for long-term use.

Environment:

  • Platform: Figma Make (web-based)
  • Issue First Noticed: April 30, 2026
  • Prior to this update: HTML file editing worked normally

2 replies

ksn
Figmate
  • Community Support
  • May 1, 2026

Hey ​@TinyDancer - thank you for posting and bringing this to our attention.

I’ve filed a bug ticket to get this checked out by the teams that work on Figma Make. I will reply here again when I receive an update on my end.


TinyDancer
  • Author
  • New Member
  • May 7, 2026

Thank you, I really appreciate this follow-up.