Optimize build by separating development and production fixtures

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

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

enhancement

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/web-forms-demo

All issues in getodk/web-forms-demo

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.