oddbird / oddbird/css-anchor-positioning
Should the demo site use the production builds?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 493
- Forks
- 18
- Avg merge
- 12h 37m
- Merged PRs (30d)
- 5
Description
The demo site is currently being bundled and built as a separate build step, which means it isn't actually running the production code. This seems like an easy way to miss production bugs (e.g. #311). I think we should look into having the demo site use the production build of the polyfill.
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 comparing how the demo site is bundled with how the production polyfill build is produced. The work is done when the demo runs the production build rather than a separate development build, allowing production-specific bugs such as #311 to surface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100