Prefresh

• core
• gatsby
• next
• nollup
• preact-cli (--refresh)
• snowpack
• utils
• vite
• webpack

Note that there is a known issue when combined with preact-devtools that the hookState does not correctly reset.

Best practices

The general best practices are linear to other hot-reloaders and concepts. Aim at making your components recognizable, so start them with a capital, if you're using custom-hooks start them with "use" and then a capital letter. If you're sharing hooks between components don't export them from the same place you're exporting components from. This could lead to stale occurences in other components.

Example:

/

• Counter.js --> The Counter component
• BigCounter.js --> The BigCounter component
• sharedHooks.js --> useCounter

Note that a component like this

export default () => {
  return <p>Want to refresh</p>
}

won't be seen as a component because there is no way for prefresh to derive the name of this component. This can be solved by doing:

const Refresh = () => {
  return <p>Want to refresh</p>
}

export default Refresh;

When you are working with HOC's be sure to lift up the displayName so we can recognise it as a component.