Skip to main content
Most Illegalcord issues are easier to solve if you identify the layer first: dependencies, build output, desktop injection, web extension output, plugin state, or settings data.

​
Dependency install fails

1

Check Node.js

Run node -v. Use Node.js 22 or newer.
2

Use the lockfile

Run dependency install from the repository root:
3

Avoid mixed package managers

Do not install dependencies with npm install or yarn in this repo. The project is configured for pnpm.

​
Desktop build fails

Run the build directly so you can read the first error:
Then run targeted checks:
Patch failures are often caused by Discord changing bundled code. Use DEV output and Patch Helper when available to inspect the nearby source.

​
Illegalcord does not appear in Discord settings

1

Confirm the desktop bundle builds

Run pnpm build and make sure it completes.
2

Run the injector

Run pnpm inject from the repository root.
3

Fully restart Discord

Quit Discord completely, including tray or background processes, then launch it again.
4

Repair if needed

If the settings section still does not appear, run:

​
Web build output is missing

Build the web target:
Then inspect dist. If the build fails, run:
Browser extension loading rules vary by browser. Make sure you are loading the generated extension output supported by your browser.

​
A plugin breaks the client

1

Disable the last changed plugin

Open Illegalcord Settings > Plugins if the UI still loads, then toggle off the plugin you changed most recently.
2

Restore from backup

If you exported a settings backup, restore a known-good plugin configuration from Backup & Restore.
3

Check the console

Open Discord DevTools and inspect the Console for the plugin name and stack trace.
4

Fix source and rebuild

Edit the plugin source, run pnpm build, then restart Discord.

​
A theme or QuickCSS breaks the UI

If the UI is still usable, open Themes or Edit QuickCSS and remove the last CSS change. If the UI is not usable:
  1. Open the settings folder from a previous known-good client if possible.
  2. Remove the broken local theme file or clear the QuickCSS backup data you imported.
  3. Rebuild and relaunch.
Keep exported backups before large theme edits. CSS can hide controls you need to recover.

​
Plugin metadata looks stale

After adding, moving, renaming, or removing plugins, regenerate plugin metadata:
If you only changed one source family:

​
TypeScript alias imports fail

Check tsconfig.json for the alias you are using. Common aliases include @api/*, @components/*, @utils/*, @webpack, @webpack/common, @plugins/*, and @equicordplugins/*. Avoid deep relative imports when an alias exists.