Going to React 18 and vitejs

[evan-boissonnot]

Thanks for filing a bug! To save time, if you're having trouble using the library, please check off the items you have tried. If you are just asking a question, skip right to the bottom.

Please verify these steps before filing an issue, and check them off as you go

• The relevant native JavascriptEngineSwitcher library packages are installed (such as JavaScriptEngineSwitcher.V8.Native.win-x64)
• The VC++ 2017 runtime is installed
• The value of SetUseReact and SetUseBabel is correct in ReactConfig.cs or Startup.cs
• I've looked at the sample projects in this repo to verify that my app is configured correctly

I'm using these library versions:

• ReactJS.NET:
• JavaScriptEngineSwitcher:
• react and react-dom: (N/A if using bundled react, or version number)
• webpack: (N/A if using bundled react)
• node: (N/A if using bundled react)

Runtime environment:

• OS: (Mac, Windows, Linux flavor. Include 32-bit/64-bit and version)
• .NET Framework or .NET Core Version:

Steps to reproduce

---

How, I'm using the last version of React.net .. that is really old. 4 years.
Please could you update the react and all config for last professionnal support :

• React 18 (and preparing to react 19 soon)
• stop using webpack : it's too old, and monster to do someting easy
• use instead : vitejs
• stop prefer js at begining : starting with typescript

[ibakirov]

@evan-boissonnot IMHO do not expect any future updates for ReactJS.NET and refer to #1315. I suggest splitting your React application from .NET and then you free to go switching to vitejs, typescript and other new React versions (as I did for one legacy project where removed ReactJS.NET).