expressjs / expressjs/discussions
EFI: Shared configuration
- Dominant language
- No language data
- Stars
- 73
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
### Motivation
Like actions, we have multiple configuration in all projects, from a normal eslint setup to more advanced solutions. With our current way to implement it, it means that if we want to update and change a rule we need to update a lot of projects to be consistant.
By creating and having a package for all shared config (or multiple) we could leverage that to automatically update the configurations
### Expectation
Move all configurations in a repository that package the configuration
### Implementation
Create a package (or multiples) for reusable configuration
- eslint
### Status
Part: Technical
Status:
- create eslint package
### Draft
> All packages in the same organization should be following the same standards, it would make almost no sense to have the same configuration re-defined in each repository. By creating and exporting said configuration (for linting or other tools) this would allow us to enforce the same rules everywhere without risk.
Contributor guide
Assessment
This issue has not been assessed yet.