Feature Ideas:

[Adesoji1]

1. Component Library: Developing a library of common UI components that users can easily import and use in their projects.

2. State Management: Implementing a state management feature similar to Redux in ReactJS could be beneficial for managing application state.

3. Routing: A built-in routing system could be an excellent addition for building more complex, multi-page applications.

4. Hot Module Replacement: This feature would help developers by automatically refreshing the page when changes are made to the code.

5. Server-Side Rendering: Implementing server-side rendering could improve performance and SEO for applications built with ReactPy.

[Archmonger]

1. We plan on allowing users leverage existing component frameworks from NPM in an easier fashion.
   • Better compatibility with ReactJS Packages #786
2. This should be an external package but it is a good idea. Would be nice if the community developed this.
3. This already exists in the form of reactpy-router
   • https://github.com/reactive-python/reactpy-router
4. This can be achieved via file watching in many popular webservers such as Uvicorn
5. This is planned
   • SEO Compatible Rendering #578

[rmorshea]

For 3, we should enable that by default when using reactpy.run. I think there's an issue for that already.

[Adesoji1]

@rmorshea for number 5, how can i assist with its implementation in terms of writing code, testing the feature, or updating the documentation once or before it's complete.

[Archmonger]

We have an fairly detailed thought process lined out in #578

It's fairly complicated and will require deep knowledge of ReactJS, SSR rehydration, and Jinja2. You're free to take a stab at it but we haven't had time to fully confirm what is/isn't possible.

[rmorshea]

It's perhaps worth noting that everything is already rendered server-side. The main problem the linked issue describes has to do with SEO and the fact that the initial page load just contains a JS blob. Unfortunately, a path forward on this SEO issue hasn't been laid out yet so I don't think I can give you any specific direction on what to do in terms of developing that feature. Of course, once it has been developed documentation and early testing would be much appreciated.

There's a lot of things that are up in the air at the moment and we're trying to figure out exactly what to prioritize. If you leave a comment on that issue expressing interest in helping, you'll be in the loop as we determine the best approach to take. Any input you have in that regard would also be helpful.

[rmorshea]

Based on @Archmonger's comment I may not be recalling everything that we've been thinking about with respect to SEO, so it's possible that there's some concrete exploration or actions that could be done.