Empresas
Empregos
  • Sobre nós
  • Soluções
    • Publicação de vagas
      Publique sua vaga e receba candidatos qualificados em 48h.
    • Avaliações de candidatos
      Mais de 500 testes técnicos e psicológicos, mais anti-fraude.
    • Headhunting
      Busca executiva personalizada do início ao fim.
    • Folha de Pagamento + EOR
      Dispersão de folha e EOR em mais de 15 países da LATAM.
  • Preços
  • Empregos

0

623
Visualizações
¿Por qué mi compilación de Gatsby falló en Error: ENOENT: no existe tal archivo o directorio?

Estoy generando un sitio de Gatsby que funciona bien con el desarrollo de Gatsby, pero al crearlo, se genera un error.

 success Building production JavaScript and CSS bundles - 26.183s ⠇ Building Rendering Engines [ ] 45.509 42/47 9 Running gatsby-plugin-sharp.IMAGE_PROCESSING … s 7 % <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (11572kiB) impacts deserialization performance (consider using Buffer instead and decode when needed) <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (11572kiB) impacts deserialization performance (consider using Buffer instead and decode when needed) ⠙ Building Rendering Engines [ ] 64.883 44/47 9 Running gatsby-plugin-sharp.IMAGE_PROCESSING … s 7 % <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (127kiB) impacts deserialization performance (consider using Buffer instead and decode when needed) <w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (127kiB) impacts deserialization performance (consider using Buffer instead and decode when needed) success Building Rendering Engines - 69.787s success Building HTML renderer - 70.287s success Execute page configs - 0.050s failed Validating Rendering Engines - 73.109s ERROR #98001 WEBPACK Built Rendering Engines failed validation failed validation. Please open an issue with a reproduction at https://github.com/gatsbyjs/gatsby/issues/new for more help Error: ENOENT: no such file or directory, open 'C:\Users\UCHE\Desktop\own-r eview\site\.cache\query-engine\interfaces.gql' - node:fs:585 Object.openSync node:fs:585:3 - node:fs:453 Object.readFileSync node:fs:453:35 - index.js:708656 Object.<anonymous> C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:708656 :17 - index.js:734538 __webpack_require__ C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:734538 :42 - index.js:708375 Object.<anonymous> C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:708375 :19 - index.js:734538 __webpack_require__ C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:734538 :42 - index.js:708334 Object.<anonymous> C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:708334 :22 - index.js:734538 __webpack_require__ C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:734538 :42 - index.js:708328 Object.<anonymous> C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.js:708328 :37 - index.js:734538 __webpack_require__ C:/Users/UCHE/Desktop/own-review/site/.cache/query-engine/index.

Traté de reconstruir después de ejecutar gatsby clean, eliminé el archivo .cache, reinstalé node_module pero aún no tuve suerte

Alguien sabe como puedo solucionar este error?

about 4 years ago · Juan Pablo Isaza
1 Respostas
Responde à pergunta

0

intente eliminar el directorio .cache en su proyecto gatsby y ejecute yarn start o yarn build nuevamente (o los comandos npm equivalentes si está usando npm ), esto resolvió todos los problemas relacionados con webpack.cache.PackFileCacheStrategy para mí...

about 4 years ago · Juan Pablo Isaza Relatório
Responde à pergunta
Encontrar trabalhos remotos

Descubra a nova forma de encontrar um emprego!

melhores empregos
Principais categorias de trabalho
Empresas
Postar vaga Preços Comercial
Jurídico
Termos e Condições Política de privacidade
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomende algumas ofertas para mim
Preciso de ajuda