tiny-pilot / tiny-pilot/tinypilot
Setup bundling for frontend assets (JS, CSS)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
We're currently storing different assets in different files, which is starting to add latency to TinyPilot's initial page load. This is a consequence of the fact that we're not using any modern JS framework that would bundle everything together for us.
We should look at options for bundling JS and maybe CSS to reduce initial page load times and allow us to better use JS modules, which will allow us to do unit testing more easily.
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
The issue names no files, tests, or asset entry points. Start by locating how TinyPilot currently loads its JavaScript and CSS, then compare bundling options against initial page-load latency and module testing needs; done means an agreed bundling approach is implemented and its impact is measured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- build-system, frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100