Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

334
Views
error ENOENT DE RECHAZO NO MANEJADO: no existe tal archivo o directorio, abra '/vercel/path0/.cache/json/

Estoy ejecutando una solicitud de recuperación dentro de un bucle for, la API que estoy obteniendo es un servidor heroku que extrae datos y los envía de vuelta con res.json(). El servidor heroku es una versión gratuita. El código que falla en el nodo gatsby (async createPages) se muestra a continuación

 const laro = await graphql(`{ links { results } } `) await laro.data.links.results.forEach( async kok => { try { let luca = await kok.split("/")[4] let rollot = await fetch( `https://sheltered-meadow-66603.herokuapp.com/noti/${luca}`) await createPage({ path: `/${luca}/`, component: abruNews, context: { data: rollot, }, }) } catch (err) { console.log(err) } })

el error que me sale es este

 For more info and debugging tips: see https://gatsby.dev/sync-actions File /vercel/path0/gatsby-node.js:232:14 230 | ) 231 | > 232 | return createPage({ | ^ 233 | path: `/${luca}/`, 234 | component: abruNews, 235 | context: { success Building production JavaScript and CSS bundles - 48.439s success Rewriting compilation hashes - 0.001s error UNHANDLED REJECTION ENOENT: no such file or directory, open '/vercel/path0/.cache/json/_abruzzo-esperienziale-un-viaggio-nei-cinque-sensi-nelle-terre-dei-briganti_.json' Error: ENOENT: no such file or directory, open '/vercel/path0/.cache/json/_abr uzzo-esperienziale-un-viaggio-nei-cinque-sensi-nelle-terre-dei-briganti_.json' npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! gatsby-starter-default@0.1.0 build: `gatsby build` npm ERR! Exit status 1 npm ERR!

Gracias si puedes ayudar

about 4 years ago · Juan Pablo Isaza
1 answers
Answer question

0

Un bucle for (en lugar de forEach) parece ser mejor para finalizar cada solicitud y el error desapareció

about 4 years ago · Juan Pablo Isaza Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!