approvals / approvals/Approvals.NodeJS
Remove dependency on ts-node
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 125
- Forks
- 46
- Avg merge
- 2m
- Merged PRs (30d)
- 16
Description
Hello. Just recently I found that approvals require ts-node when running using npx without local install.
Why is ts loader required at runtime anyway? Ideally, it should not be needed.
If it cannot be removed, would you accept a PR with a script that runs with tsx or ts-node depending on which one is available in the given project?
Contributor guide
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
Start with the npx execution path and trace why ts-node is required at runtime. Compare whether the package can run without it or needs a tsx/ts-node fallback; done means the runtime dependency is removed or the accepted fallback behavior is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100