Welcome to @lazarv/react-server Discussions!

[lazarv]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[ericdmachado]

Hello everyone, I'm Eric, a software developer in Brazil focused on frontend, I found this beautiful project when I was looking for a simpler alternative to Next that could help me transition a project I'm developing in React+Vite. I started reading all the documentation and it's really a great job.

[lazarv]

Hi @ericdmachado! Thanks for giving this framework a chance! Please let me know if there's any issue migrating your project or any way I can help with using @lazarv/react-server.

[CharidimosTzedakis]

Hello there! I am Charidimos, a software engineer working on frontend, in Athens Greece. I find this project really interesting and would like to dive into and learn how to contribute, since I would love to combine working on newest react features tooling together with a vite and rollup deep-dive.

Currently I try to debug the code of the project while running examples to understand the structure and also keep up with the new PRs that are opened. I also try to checkout the developments to vite's Environment API.

[lazarv]

Hi @CharidimosTzedakis! Welcome and thanks for checking out this framework!

I'm grateful for any type of contributions. It could be just feedback, issue reports or even PRs are welcome. The project is trying to be transparent and open as possible.

Using Vite's new Environment API helped the project a lot, but as I have a non-standard setup here the implementation should not be considered as an example. All this is because how this framework resolves to it's own React packages and that it supports running your app using npx or via stdin piping.

If there's desire from the community to get a deep dive in how the framework works under the hood to get a better understanding on the architecture (including Vite Environment API usage) then I could publish a blogpost about it in the future. I'm already planning to do so about RSC Delegation which supports the micro-frontend features.

[CharidimosTzedakis]

Thanks a lot for the reply!

Ok i see the point regarding the new Environment API. For me, i think it would be beneficial to have some blogposts/description of the framework architecture and how it works in a more high-level approach.