Don't include development assets in Python package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem? Please describe.
The dash-renderer sdist on PyPI is quite big large (2.3M compressed, 10M uncompressed) compared to the actual required components. This is due to at least the following files that shouldn't be required:
dash_renderer.dev.js(3.9M)dash_renderer.dev.js.map(4.5M)dash_renderer.min.js.map(1.3M)
Describe the solution you'd like
Don't distribute files for development purposes in release artifacts. This would reduce the size of the package to 1/10 (200K compressed, 720K uncompressed).
Describe alternatives you've considered
As an alternative to not shipping the debug maps at all, you could also distribute them as separate -dbg packages. This would enable a user to get debug information but not having these files in all installations. This requires a lot more effort though.
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 by locating how the dash-renderer Python package builds its release artifact and where dash_renderer.dev.js, dash_renderer.dev.js.map, and dash_renderer.min.js.map are included. Produce a package without development assets and verify that the resulting sdist contains the required runtime files and is substantially smaller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100