Lint configuration packages.
| Package | Description |
|---|---|
| @dyrkow/editor-config | EditorConfig preset; run yarn editor-config to generate .editorconfig. |
| @dyrkow/eslint-config | Base ESLint config (always extend first). |
| @dyrkow/eslint-config-react | ESLint config for React and React Hooks. |
| @dyrkow/eslint-config-react-native | ESLint config for React Native. |
| @dyrkow/eslint-config-typescript | ESLint config for TypeScript. |
| @dyrkow/prettier-config | Shared Prettier config. |
Each package README has Installation and Configuration sections.
When using react, react-native, or typescript configs, the consumer explicitly installs @dyrkow/eslint-config (the base) and the configs they need — so the project’s package.json clearly shows the dependency on the base. Shared versions (eslint, prettier, typescript, @typescript-eslint/*) are kept the same in the base and related packages so that monorepos get a single resolved version and no duplicates.
This repo is a Yarn workspaces monorepo with Nx for task orchestration and Changesets for versioning and changelogs. Each package is versioned independently.
-
After making changes: run
yarn changesetto add a changeset. Choose the package(s), bump type (major/minor/patch), and a short description. A markdown file is added under.changeset/. -
Before releasing: run
yarn run versionto apply changesets, updatepackage.jsonversions and generate CHANGELOGs. -
Publishing: run
yarn release(runschangeset versionthenchangeset publish) to publish updated packages to npm. Packages are published withaccess: "public".
See .changeset/README.md and the Changesets docs for more.
- List projects:
npx nx show projects - Dependency graph:
npx nx graph - When you add build/lint tasks, use
nx run-many -t <target>ornx affected -t <target>for cached runs. The default comparison branch foraffectedismain(seenx.json).
