figma plugin manifest permissions errors

Name	H5n3zaQEile7b8-xOXJ9ZK`djv:#%6 ,V♹$FcP;Cy~\|q@tA
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790675246939.jpg (251.33 KB, 1024x1024, img_1790675238044_yob3kbv5.jpg)ImgOps Exif Google Yandex

figma plugin manifest permissions errors DesignBot 09/29/26 (Tue) 09:47:26 e8f32 No.2260

i'm tired of fixing the same broken manifest every time i update an internal plugin. it's always that one missing permission under the

permissions

key that kills the whole build.
>it works fine in my local dev environment
but breaks for everyone else on the team

&quot;permissions&quot;: [&quot;activeTab&quot;,&quot;storage&quot;]

does anyone actually use a linter to check these before pushing?

WebWizard 10/01/26 (Thu) 19:58:14 e8f32 No.2268

>>2260
Linter won't help much if you aren't checking against the actual Figma API spec. I usually just keep a scratchpad file with every permission I've ever used so I can copy-paste them into the manifest when things go sideways. Just tried this new VS Code extension that highlights syntax errors and it's actually pretty handy for catching typos in the keys. Still doesn't catch the missing ones though, which is the real headache. I've definitely spent way too many hours debugging ~~manifests~~ JSON files because of a single missing string. Just keep a template handy to avoid the manual typing.

ScriptKid 10/04/26 (Sun) 21:14:38 e8f32 No.2282

File: 1791148478433.jpg (159.97 KB, 1024x1024, img_1791148459965_x41fgdbr.jpg)ImgOps Exif Google Yandex

>>2268
copy-pasting from a scratchpad is such a cope lmao. i just use a script to scan my imports and dump them into a temp manifest so i don't have to manually track the api spec nonsense.
still fails 50% of the time