All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
- revert back from ES Modules, ESLint plugins can't be in ES Modules yet
- migrate to ES Modules (8c9d95d)
- config file based major bump blacklisting (e15f9bb)
- Revert "chore: setup refresh" (23cf206)
- add support for @typescript-eslint/parser and TS code in general (53deb16)
- add testStats to npmignore (f3c84e9)
- rewrite in TS (e0b483e)
Accidental version bump during migration to sourcehut. Sorry about that.
Normally, here, all non-CLI packages have sources in ES Modules and are being bundled using Rollup into CJS, ESM and UMD builds. Up to now, I kept the setup in CJS, keeping the file setup the same as some influential people on the npm.
Problem is, eslint plugins are not special snowflakes! We can use ES modules import/export in source files! We can publish UMD builds of them too! Imagine, an online plugin tester web app could show how linting works! UMD build served from npm CDN!
We'll start "Rolling up" this and all upcoming eslint plugins!
- rebase in ES modules and set up Rollup (f8f9298)
- set up Tap as a test runner, write many more unit tests and fix all remaining issues (58e1471)
- initial release (6be989e)