Alteast not including in 4.30. Here is the list of upcoming nop features.
This is not a list of upcoming feautres. It's just a wish list of users. The only one, real list of features that are approved by Andrei and nopCommerce Team can be found here, on nopCommerce GitHub page: https://github.com/nopSolutions/nopCommerce/milestone/6.
I have been working on nopCommerce projects for about 2 years now, and I'd say that doing something like this does not require that much changes to the source code. At our projects we started to move away from returning views in our plugins to returning pure JSON, either through an endpoint or setting it on the window object. Then we have react in the frontend which hydrates components with that data, so it's not a big task to do yourself. However, changing every part of the site views to use react took quite a long time but you can definitely do it for smaller parts and ultimately replace more of the original frontend as you go. We also use webpack, scss, TypeScript and have an UI (also TS) etc.
The way we went about this primarily is that we keep alot of the original stuff, we don't render a full SPA page as you normally would with react/other frameworks, instead, we use the render function from react to render our new components into certain places.
Another alternative would be to go headless, in that case you can just deploy your SPA as normal, however you would then have to spend a lot of time reimplementing alot of nopCommerce features.
I have been working on nopCommerce projects for about 2 years now, and I'd say that doing something like this does not require that much changes to the source code. At our projects we started to move away from returning views in our plugins to returning pure JSON, either through an endpoint or setting it on the window object. Then we have react in the frontend which hydrates components with that data, so it's not a big task to do yourself. However, changing every part of the site views to use react took quite a long time but you can definitely do it for smaller parts and ultimately replace more of the original frontend as you go. We also use webpack, scss, TypeScript and have an UI (also TS) etc.
The way we went about this primarily is that we keep alot of the original stuff, we don't render a full SPA page as you normally would with react/other frameworks, instead, we use the render function from react to render our new components into certain places.
Another alternative would be to go headless, in that case you can just deploy your SPA as normal, however you would then have to spend a lot of time reimplementing alot of nopCommerce features.