wtf is eslint-plugin-erasable-syntax-only?

Node.js recently added the ability to run TypeScript files directly, without a separate compilation step. But there's a catch: Node can only handle "erasable" TypeScript code, meaning features that can be simply stripped away to leave plain JavaScript. Some TypeScript features, like enums, namespaces, and certain class parameter shortcuts, don't work this way and will cause errors. This ESLint plugin helps teams catch those problematic patterns in their code before they become a problem. The tool works as an add-on for ESLint, a popular code-checking utility. Once installed, it flags four specific TypeScript features that aren't erasable: enums, import aliases, namespaces, and class parameter properties. Some of these issues can even be auto-fixed by your editor. The plugin gives you four separate rules you can turn on individually rather than forcing an all-or-nothing switch. This is primarily for teams with an existing TypeScript codebase who want to migrate toward running their code directly through Node.js without a build step. If your project is large and uses enums or namespaces throughout, you can't just flip a switch, you'd have hundreds of errors at once. This plugin lets you tackle one rule at a time, exclude certain files temporarily, and add inline comments to suppress specific warnings where needed. It turns an overwhelming migration into a gradual cleanup. Notably, if you've already enabled TypeScript's own --erasableSyntaxOnly compiler flag, you don't need this plugin at all. The value here is the flexibility: TypeScript's flag is project-wide, while this plugin lets you be surgical about which rules apply where. The project requires ESLint version 9 or higher and Node.js 20.18.0 or newer.