Context
Each repo in the org currently maintains its own Prettier configuration. Pulling this into @w3-kit/config as a published subpath (e.g., @w3-kit/config/prettier) gives every repo a single source of truth and a one-line consumption pattern.
What to build
Add a prettier.config.cjs (or .json) to this repo exporting the project's preferred Prettier settings, then expose it via the package's exports map under ./prettier. Update the README to show how to consume it from any downstream repo:
// prettier.config.js
module.exports = require('@w3-kit/config/prettier')
Acceptance criteria
Pointers
Complexity
🟢 Good first issue
Context
Each repo in the org currently maintains its own Prettier configuration. Pulling this into
@w3-kit/configas a published subpath (e.g.,@w3-kit/config/prettier) gives every repo a single source of truth and a one-line consumption pattern.What to build
Add a
prettier.config.cjs(or.json) to this repo exporting the project's preferred Prettier settings, then expose it via the package'sexportsmap under./prettier. Update the README to show how to consume it from any downstream repo:Acceptance criteria
@w3-kit/config/prettierpackage.jsonexportsfield updatedPointers
tsconfig/ eslint exports in this repoComplexity
🟢 Good first issue