developit / developit/workerize-loader
Breaks on latest gatsby, only when there is a webpack cache
- Lenguaje dominante
- JavaScript
- Estrellas
- 2.3k
- Forks
- 85
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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?
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Create the minimal reproduction with a newly bootstrapped Gatsby project, then start the Gatsby dev server twice with webpack caching enabled. Compare worker loading and the exported worker functions before and after clearing webpack's cache; done means the worker loads with its exported functions on the cached restart.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript, webpack
- Área
- build-system
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100