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

117
Visualizações
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 Respostas
Responde à pergunta

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 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