React.NET icon indicating copy to clipboard operation
React.NET copied to clipboard
verified publisher icon reactjs

Going to React 18 and vitejs

Open evan-boissonnot opened this issue 1 year ago • 3 comments

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

evan-boissonnot avatar Oct 28 '24 10:10 evan-boissonnot

@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).

ibakirov avatar Nov 24 '24 12:11 ibakirov

You can use whichever bundler you want to generate the JS files for your app btw. If you want typescript then fork the template of the example app with typescript and feel free to make it public to help others to get started.

@ibakirov regarding splitting your front end from .NET, do you essentially lose all of your c# nice stuff when you do that, for instance, authentication?

coultonluke avatar Aug 24 '25 19:08 coultonluke

@coultonluke No .NET part remains as Backend API with nice features of API Authorization. Your Frontend is only need to pass auth tokens when interacting with .NET Backend API

ibakirov avatar Aug 27 '25 09:08 ibakirov