developit / developit/workerize-loader

Breaks on latest gatsby, only when there is a webpack cache

Open
#131 6 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2.3k
Forks
85
PR merge metrics
No merged PRs in 30d

Description

It seems like after I start the Gatsby dev server a second time — and webpack has a cache — the worker doesn't load with the exported worker functions set on the object. The moment I clear webpack's cache and restart the dev server, the worker loads fine again.

Does this very limited description by any chance give you a quick insight about what might be causing this?

I'm afraid I can't really give more details, because the inner workings of gatsby/webpack is just one big black box to me.

I can of course make a minimal reproduction with a newly bootstrapped gatsby, if this would be of any help?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.