int128 / int128/typescript-action
Migrate to ESM
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 2
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 37
Description
git checkout -B migrate-esm
mv eslint.config.mjs eslint.config.js
cp ../typescript-action/jest.config.js .
cp ../typescript-action/tsconfig.json .
perl -i -p -e 'if (/^import/) { s/from '\''\.(.+)'\''/from '\''.$1.js'\''/g }' **/*.ts
perl -i -p -e 's/"dependencies": \{/"type": "module",\n "dependencies": \{/' package.json
pnpm lint
pnpm test
git add .
git commit -m 'Migrate to ESM'
gh pr create -f --body '- https://github.com/int128/typescript-action/issues/782'
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
Start with eslint.config.mjs, package.json, the copied jest.config.js and tsconfig.json, then review the relative imports in the TypeScript files. Run pnpm lint and pnpm test after applying the migration steps; done means the ESM configuration is in place and both checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100