mixmaxhq / mixmaxhq/multibuild
Concurrent builds of watched files in the same cache group can cause corruption
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is due to how we modify the cached modules in the post-build callback.
Error: Could not load <redacted remote import> (imported by <redacted root shim>): ENOENT: no such file or directory, open '<redacted remote import>'
at .../node_modules/rollup/dist/rollup.js:21385:19
at <anonymous>
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
Error: Could not load underscore (imported by <redacted>): ENOENT: no such file or directory, open 'underscore'
at .../node_modules/rollup/dist/rollup.js:21385:19
at <anonymous>
Error: Could not load backbone (imported by <redacted>): ENOENT: no such file or directory, open 'backbone'
at .../node_modules/rollup/dist/rollup.js:21385:19
at <anonymous>
cc @wearhere
Contributor guide
No contributing guide indexed for this repository
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 at the post-build callback that modifies cached modules and reproduce concurrent watched-file builds sharing a cache group. Done means those builds no longer corrupt the cache or produce the reported ENOENT module-load failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rollup
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100