Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

118
Vistas
Can unnecessary React.Fragment be poor in performance?

Recently, I found that our company's code performance is poor. As I reviewed code, there's so many codes like this:

condition ? <SomeComponent /> : <></>

They use Fragment as replacement of null. Can this code occur performance problem?

about 4 years ago · Juan Pablo Isaza
1 Respuestas
Responde la pregunta

0

It's unlikely that the fragments are causing (if any) noticeable performance issues. As this answer highlights, fragments don't actually create an extra DOM node.

With that said, the react docs do suggest using null when you don't want a component to render at all, but again I don't think using them would be the root cause of any slowness in your app.

I'd look at potential unnecessary re-renders, especially in nested child components being re-rendered by parent components with state changes happening.

I'd also definitely a look at the React Profiler and use it to get a sense of what's causing any performance issues.

about 4 years ago · Juan Pablo Isaza Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda