build-watch takes too long and keeps running without any changes made
Open
Nobody has claimed this yet.
type - bug
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
The build-watch command seems to be broken. I got a fresh copy of CesiumJS on the main branch and ran npm run build then npm run build-watch. I did not make any changes to the code and still, build-watch kept running with build taking forever to complete.
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 reproducing the behavior from a fresh CesiumJS main checkout with npm run build, followed by npm run build-watch, without changing any files. Trace the entry points behind those npm scripts and determine why the watch build continues or takes too long with no changes; done means an unchanged checkout completes normally and remains idle until a file changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100