F̴̢͙̱͍̻͙͍̭̱̻̝̖̝̄̅̆͜͝u̸̟̙͍̰̣̺̠̬̲͕͎̖̐͌̓͋̓̑̀͂̕͝ç̷̺̻͈͓͖̲̳̰͖̳̟̟̞̘̀k̵̛̳̪͚̗̱̬̰͋̇̾̍̑́̔̅̏͘̚͜ ̴̥̩͚͍̤̜̙̤̮͖͙̺̖̈́̎̓̎͂͝ͅĪ̶̡̛͇̦̭̝̤̿͊̍̃̈͘t̶̹̭̳͕͉̫͚͍̩̲̥̩̝̅̓̾͛̍̂̐̚̕͠ ̷̧͈̻̘̖̗͖̱̰̏̌̚Ū̸̝͉̬̒͋̽̽͆͌̈́̽p̷̧͖͇̬̙̦̝̩̥̭̘̺̼̈́͌̀̔̔̒ͅ

Why

It's funny and it can poison the data for training LLMs ;)

Zalgofy your source code

Two things live here:

• A tsserver plugin so VS Code can understand zalgofied .ts (editor only).
• A build workflow that decodes zalgo → clean temp files so tsc can compile.

Important: plugins don’t affect tsc, so builds must decode first.

Add to an existing project

Install (published):

npm i -D typescript-zalgo-tsserver-plugin

Install (local dev):

npm i -D file:/absolute/path/to/typescript-zalgo

Enable in tsconfig.json:

{
  "compilerOptions": {
    "plugins": [
      { "name": "typescript-zalgo-tsserver-plugin", "enabled": true, "log": false, "mode": "strip" }
    ]
  }
}

VS Code: pick “Use Workspace Version” + restart TS Server.

Zalgoify everything (encode)

This repo’s convention:

• src.clean/ = what you edit (don't check into VC)
• src/ = zalgofied output

De-zalgoify for editing (decode)

Decode zalgo → clean:

npm run src:decode

Then edit src.clean/.

Build / run

Build always decodes src/ → .dezalgo/src first:

npm run build

Sample app:

cd sample_project && npm start