Consider removing sourcemaps from publish
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 402
- Avg merge
- 1m
- Merged PRs (30d)
- 18
Description
Given that the published code is itself readable (it is just type-stripped), one could argue we don't really need sourcemaps.
A minority of users will be debugging their node_modules, but all users pay the price. So it seems worthwhile.
Stats:
- Packed size: 44KB -> 34KB
- Unpacked size: 235KB -> 173KB
happy to open a PR if you're in agreement
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 by locating the repository's publish and sourcemap configuration, then inspect how the package is built and packed. Confirm which published artifacts include sourcemaps and compare packed and unpacked sizes after the change. Done means published code no longer includes sourcemaps while the readable type-stripped code remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100