vercel-labs / vercel-labs/bash-tool
Provide a CJS build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 622
- Forks
- 43
- Avg merge
- 22m
- Merged PRs (30d)
- 1
Description
I hate to even raise this one, but we have a large codebase that even with LLMs will take quite a bit of effort to move onto the esm ecosystem. I've had some success getting bash-tool to work with dynamic imports, but getting it fully working (tests and all) is a bit of a challenge.
It'd make it much easier to experiment with this (and just-bash) if it wasn't blocked on overhauling our monorepo 😅
Totally understand if you don't want to do this, it might make maintenance more trouble than it's worth for you.
(there's a similar ask for just-bash, but asking in one place first)
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 monorepo's current ESM build configuration and test setup, then determine how a CommonJS artifact would be produced and consumed. Done means a CJS build is available and the existing tests still work with it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100