Update limitations section README.md [publish]

Author: ArnaudBarre

README.md

@@ -6,17 +6,20 @@ Validate that your components can safely be updated with fast refresh.
 
 ⚠️ To avoid false positive, this plugin is only applied on `tsx` & `jsx` files ⚠️
 
-Like the implementation for [vite](https://github.com/vitejs/vite/blob/e6495f0a52c9bd2cae166934dc965f8955ce035d/packages/plugin-react/src/fast-refresh.ts#L108), the plugin rely on naming conventions (i.e. use ). This is why there is some limitations:
+Like the implementation for [vite](https://github.com/vitejs/vite/blob/e6495f0a52c9bd2cae166934dc965f8955ce035d/packages/plugin-react/src/fast-refresh.ts#L108), the plugin rely on naming conventions (i.e. use PascalCase for components, camelCase for util functions). This is why there is some limitations:
 
 - `export *` are not supported and will be reported as an error
-- anonymous function are not supported (i.e `export default function() {}`)
+- Anonymous function are not supported (i.e `export default function() {}`)
+- Class components are not supported
 - Full uppercase export would be considered as an error. It can be disabled locally when it's effectively a React component:
 
 ```jsx
 // eslint-disable-next-line react-refresh/eslint-plugin-react-refresh
 export const CMS = () => <></>;
 ```
 
+I may publish a rule base on type information from [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint) to improve some limitations and catch some naming convention issues (like non-component function starting with an uppercase).
+
 ## Installation
 
 ```sh

package.json

@@ -1,7 +1,7 @@
 {
   "name": "eslint-plugin-react-refresh",
   "description": "Validate that your components can safely be updated with fast refresh",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "license": "MIT",
   "author": "Arnaud Barré (https://github.com/ArnaudBarre)",
   "main": "src/index.js",