overengineeringstudio / overengineeringstudio/effect-utils
Track unifying Effect LSP task with ts:check under tsgo
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
We currently expose the Effect LSP diagnostics as a standalone devenv task.
Longer term, once the repo-wide TypeScript check moves from tsc --build to Effect-TS/tsgo --build, we should fold this standalone task into the normal ts:check flow instead of maintaining a parallel task.
Target end state:
ts:checkis tsgo-backed- the separate Effect LSP check task is removed
- downstream repos consume one TypeScript check path instead of two partially overlapping ones
This issue is only for tracking that unification work. It is not the same as the current namespace migration or the current tsgo bug fixes.
Filed by an AI assistant on behalf of @schickling
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the standalone Effect LSP diagnostics task and the normal ts:check task, then trace how each invokes TypeScript checking. Done means ts:check uses tsgo, the separate Effect LSP check task is removed, and downstream repositories have one TypeScript check path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100