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

323
Views
Next.js: las funciones de flecha anónimas hacen que Fast Refresh no conserve el estado del componente local (advertencia)

Actualmente estoy experimentando esta advertencia que apunta a un objeto sin nombre en un archivo de configuración, y nombrarlo no resuelve la advertencia. A continuación se muestra la advertencia detallada y ejemplos.

Advertencia:

 Anonymous arrow functions cause Fast Refresh to not preserve local component state. Please add a name to your function, for example: Before export default () => <div />; After const Named = () => <div />; export default Named;

Antes:

 export const = { apiUrl: process.env.NEXT_PUBLIC_API_URL as string, commitRef: process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_REF as string, ldSdkKey: process.env.NEXT_PUBLIC_LD_SDK_KEY as string, imgixBaseUrl: process.env.NEXT_PUBLIC_IMGIX_BASE_URL as string, imgixApiKey: process.env.NEXT_PUBLIC_IMGIX_API_KEY as string, imgixResourceID: process.env.NEXT_PUBLIC_IMGIX_RESOURCE_ID as string, };

Intento de resolución ./src/config.ts:

 const AppConfig = { apiUrl: process.env.NEXT_PUBLIC_API_URL as string, commitRef: process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_REF as string, ldSdkKey: process.env.NEXT_PUBLIC_LD_SDK_KEY as string, imgixBaseUrl: process.env.NEXT_PUBLIC_IMGIX_BASE_URL as string, imgixApiKey: process.env.NEXT_PUBLIC_IMGIX_API_KEY as string, imgixResourceID: process.env.NEXT_PUBLIC_IMGIX_RESOURCE_ID as string, }; export default AppConfig;

Esperemos que alguien más haya experimentado esto y haya encontrado una solución.

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

0

Resulta que el problema era que nuestra versión anterior de Next.js no apuntaba hacia la causa correcta de la advertencia, pero aun así la mostraba. La siguiente actualización me guió hacia el código del problema y pude resolverlo.

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!