influxdata / influxdata/clockface
Build: use webpack for production and dev builds
Open
Nobody has claimed this yet.
tech debt
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 18
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 1
Description
Problem:
- We are using Rollup for production builds and Webpack for development builds (aka storybook)
- Having two build tools is hard to understand
- Makes it harder for anyone to work on Clockface if they have to rebuild context every time
- Currently experiencing some disparities between development vs production builds
- Exporting / referencing image assets is currently not working correctly
Proposed Solution:
- Replace Rollup with Webpack for production builds
- This should make it simpler to solve the image asset issue
- Also makes it simpler to implement build changes in the future
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
Locate the current Rollup production configuration and the Webpack development/Storybook configuration, then compare how each handles builds and image assets. Consolidate production builds on Webpack, preserve the required development behavior, and verify that image exports and references work consistently in both environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rollup, typescript, webpack
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100