ChainSafe / ChainSafe/lodestar

Consistent package configuration on Lodestar libs

Open
#2,459 4 comments 0 reactions 0 assignees View on GitHub
prio-low scope-none
Dominant language
TypeScript
Stars
1.4k
Forks
483
Avg merge
1d 18h
Merged PRs (30d)
156

Description

There are some actions that should be done on all Lodestar libraries that are not in the monorepo:
- [ ] Add CI: A Github Actions workflow that builds, tests and lints
- [ ] Same Typescript, linter and prettier dependency versions are used as in the Lodestar monorepo
- [ ] Same tsconfig.json is used. @3xtr4t3rr3str14l Already started on this item by setting strictNullChecks = true
- [ ] Same prettier settings are used
- [ ] Same eslintrc settings are used
- [x] Add codeowners with the entire Eth2.0 team so reviewers are asked automatically
- [ ] Review READMEs that link to the Lodestar project
- [ ] Apply README checks (i.e. what is basically outlined in https://github.com/ChainSafe/lodestar/issues/2828)

Contributor guide

Open the contributing guide

Research direction

Start by identifying the Lodestar libraries outside the monorepo, then compare their CI workflows, dependency versions, tsconfig.json, .eslintrc, Prettier settings, and README files with the monorepo. Done means the unchecked checklist items are addressed, including the README checks described in issue #2828; individual library paths and tests are not named.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, github-actions, typescript
Domain
build-system, ci-cd, documentation, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.