Optimize build by separating development and production fixtures
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- build-system
Research direction
Start by locating the build configuration and the code that includes fixtures, then compare the development and production build paths. Confirm that development still includes all fixtures while production bundles only /fixtures/preview-service, and verify the resulting production artifact size or contents.
Written by the indexing model from the issue text.
Description
Description
Currently, the production bundle includes all test fixtures, which unnecessarily increases the artifact size for the live website deployment.
Proposed Solution
Separate the build process to optimize the production output:
- Dev Build: Include all available fixtures for local testing and development.
- Production Build: Bundle only the fixtures located in
/fixtures/preview-service.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 41m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from getodk/web-forms-demo
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getodk/web-forms-demo#8 ·
All issues in getodk/web-forms-demo
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
twilio/twilio-node#1241 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hugomrdias/playwright-test#786 · 1 comment ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
WenyuChiou/agent-board#1745 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day