[Suggestion]: More concrete advice for writing Fast Refresh-compatible code
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- JavaScript
- Estrelas
- 11.8k
- Forks
- 7.9k
- Merge médio
- 1d 11h
- PRs com merge (30d)
- 11
Descrição
Summary
I'm seeking advice on writing code that is compatible with React Fast Refresh and drawing a bit of a blank. I found: https://reactnative.dev/docs/fast-refresh (NB reactnative.dev not react.dev) which has some tips but the information is not very formal.
Should the react docs contain clear information about how to structure your code for best compatibility with Fast Refresh?
Page
No response
Details
From what I've gathered, it's recommended that any file exporting a React component should not export anything else (e.g., utility functions, data) to ensure Fast Refresh functions properly, and I found eslint-plugin-react-refresh which exists to help enforce this rule.
I was surprised not to be able to find authoritative guidance on this in the official react docs.
- Is the advice I've seen in forums etc. correct, i.e. to export only 1 react component per file?
- Do the rules in eslint-plugin-react-refresh accurately reflect best practice as it stands in 2025?
- Should the react docs be more clear on what exactly is best practice in this respect?
(For background, I had to fix a number of issues when migrating our codebase (a few 10,000s loc) from preact to react and during this came across the plugin https://github.com/ArnaudBarre/eslint-plugin-react-refresh which I then enabled, which throws up many errors in our codebase (react/vite). I asked two experienced react developers if they comply with the rules as suggested by eslint-plugin-react-refresh and they seemed perplexed, suggesting that people don't structure things this way in real codebases — admittedly this is the most informal possible polling, but I couldn't point them to any particularly authoritative info to the contrary.)
As always, apologies if I have simply missed the relevant info in the docs.
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Revise as orientações vinculadas sobre React Native Fast Refresh e eslint-plugin-react-refresh e, em seguida, determine quais recomendações oficiais a documentação do React deve fornecer. O trabalho estará concluído quando houver concordância sobre as orientações recomendadas para a estrutura do código e forem definidos o conteúdo ou as alterações de página necessários na documentação.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- javascript, react
- Domínio
- documentation
- Tipo de issue
- Documentação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100