Problems in a sample project

[ericdmachado]

I created a small project to test some react-server features that I will use in my project. Here is the link to my test repository (https://github.com/ericdmachado/react-server-test) and my considerations:

1 - When using vite.config, I had a problem running the server on a different port (I intend to use environments vars). The configuration file is attached as _vite.config.js.

2 - Inside a component that uses "use client", I am trying to load a server component with the generated html, but I get an error about using async await in client components.

3 - Even without these components, using only the index with a hello world. I had problems building the project inside a Docker container (docker files and Docker compose together in the repository).

4 - I had problems using aliases to facilitate my imports in the project and avoid using relative paths. Ex.: ../../providers.

Please let me know if I used it wrong!
Thank you for your attention.

[lazarv]

Hi @ericdmachado!

I created a PR for your example repo at ericdmachado/react-server-test#1
I included some information already in the PR, but here are some more information:

1 - Most likely your issue about vite.config.js was that you used a simple alias object, could you please create an issue with your repo as a reproduction that this is currently not supported by @lazarv/react-server? Thanks in advance!

2 - You can't import or lazy load server components into client components, these server components become client components. You can pass server components to client components as component props. This is not an issue, just how client and server components work in React, you can find much more information on this topic in the Next.js documentation at https://nextjs.org/docs/app/building-your-application/rendering/composition-patterns#unsupported-pattern-importing-server-components-into-client-components

3 - Docker issue was about incorrect TTY detection. @lazarv/react-server supports stdio input as an entry point, but in Docker this doesn't work properly and thinks that it should use stdio as entry point, building an empty app, which will fail on start. Same request from me as above, please create an issue for this.

4 - As I mentioned above at the first topic, alias doesn't work for now.

Thanks for creating a test project! Any new use case provides great value and I hope the initial issues doesn't scared you away from this project!

[lazarv]

Good news @ericdmachado, it seems I was able to get rid of the resolve.alias workaround on the deep dependencies, updated the PR. Let me know is something is off, if there's a bug, please create an issue.

[ericdmachado]

That's awesome @lazarv, I tested it again here with the update from your PR and also added some things locally for testing and everything worked out really well. I'm going to add react-server to parts of my application and I intend to update a little project I built in Vue (https://planningpoker.gereon.com.br/) it's going to be great!
Thank you very much for your support!