Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v1 Roadmap #24

Open
68 of 83 tasks
dai-shi opened this issue May 5, 2023 · 23 comments
Open
68 of 83 tasks

v1 Roadmap #24

dai-shi opened this issue May 5, 2023 · 23 comments

Comments

@dai-shi
Copy link
Owner

dai-shi commented May 5, 2023 •
edited
Loading

Here are tasks that I would like to finish before v1.

Previous Versions

-v0.14.0

v0.15.0

v0.16.0

v0.17.0

v0.18.0

v0.18.1

v0.19.0

v0.19.1

v0.19.2

v0.19.3

v0.19.4

v0.20.0

v0.20.1

v0.20.2

v0.21.0

v0.21.1

v0.21.2

v0.21.3

v0.21.4

v0.21.5

v0.21.6

v0.22.0

v1-alpha

v1-beta

v1-final

  • Wait for React 19
@Aslemammad
Copy link
Contributor

Aslemammad commented May 8, 2023 •
edited by dai-shi
Loading

How about actions? I was thinking about developing a plugin for vite a while ago, Since I think it's something similar to telefunc while developing this tool with Rom Brillout.

@dai-shi
Copy link
Owner Author

dai-shi commented May 8, 2023

Actions (what I call "React Server Functions") are already implemented. I wouldn't say it's complete though.

@Aslemammad
Copy link
Contributor

Nice!

@dai-shi dai-shi mentioned this issue May 16, 2023
Merged
6 tasks
@dai-shi dai-shi pinned this issue May 23, 2023
@tom-sherman
Copy link

Anecdotally there seems to be a fairly large gap between waku's server actions and Next.js' implementation - I suppose this is expected because server actions are completely experimental in React right now.

IMO it makes sense to mark them as such (as an opt-in config option) before releasing v1.

@dai-shi
Copy link
Owner Author

dai-shi commented Jul 28, 2023

I don't think our RSF (react server function) isn't that experimental, meaning it's the same level as react server component. I suppose Next's server action does more experimental things.

That said, I would like to revisit our approach anyway, which will require some feedbacks from collaborators/contributors/users.

In any case, unless we have an official doc or RFC from React, we wouldn't be able to finalize our API, which means v1 probably won't land until then.

@tom-sherman
Copy link

tom-sherman commented Jul 28, 2023 •
edited
Loading

The problem with shipping server actions now (or before they're stable in React) is that the semantics are not specified yet. For example Next.js server actions are queued, it's impossible to execute them concurrently - not the case in Waku. There is also the integration with transitions, not sure if this is implemented in Waku.

IMO need to wait for a React RFC but only for server actions, there is already an RFC for server components and they're designated at stable by the React team.

This is why I think waku server actions behind a flag is the right way forward.

@dai-shi
Copy link
Owner Author

dai-shi commented Jul 28, 2023

Yeah, if we would release v1 before the callserver RFC, we should hide it behind a flag. For now, just noting it's not finalized would be enough. But in that sense, everything isn't finalized.

@childrentime
Copy link

@dai-shi How about SSG? And change docs website to static files.

@dai-shi
Copy link
Owner Author

dai-shi commented Aug 6, 2023

docs website is already static files.
we generate static files on build (SSG is a vague word, as people expect to generate HTML files.)

@dai-shi
Copy link
Owner Author

dai-shi commented Sep 10, 2023 •
edited
Loading

IMO it makes sense to mark them as such (as an opt-in config option) before releasing v1.

Having been working on #124, I'm getting more skeptical about the stability. (What is currently working may not work in the future.)
My gut feeling is that we should wait releasing v1 before React 18.3.0 or 19 is out.

@zouhangwithsweet
Copy link

So waku will not use react-server-dom-vite in the future?

@himself65
Copy link
Contributor

So waku will not use react-server-dom-vite in the future?

I think it's up to upstream. currently react official repo only has webpack and turbopack support.

BTW, is react-server-dom-esm an alternative?

@dai-shi
Copy link
Owner Author

dai-shi commented Dec 4, 2023

It depends on what react-server-dom-vite and react-server-dom-esm will be like.

Hope the esm one is published: facebook/react#27197

@ojj1123
Copy link
Contributor

ojj1123 commented Dec 18, 2023 •
edited
Loading

Integrate React Float

@dai-shi
What is React Float? What's the relation with no index.html?

@dai-shi
Copy link
Owner Author

dai-shi commented Dec 18, 2023

Integrate React Float

@dai-shi What is React Float? What's the relation with no index.html?

I hope React docs will cover that soon. It will be called something like hoistable resource/elements.
It's technically not "integration". As #289 may tell, we no longer use index.html and add <title>...</title> in components, for example, which is possible because of hoistable elements.

@ojj1123
Copy link
Contributor

ojj1123 commented Jan 16, 2024 •
edited
Loading

I was wondering if you could explain where it is the explanation of defineEntries function in Docs or README! I couldn't find it since waku was released as v0.19.0. Is it deprecated?

@himself65
Copy link
Contributor

I was wondering if you could explain where it is the explanation of defineEntries function in Docs or README! I couldn't find it since waku was released as v0.19.0. Is it deprecated?

No, that API is still available, but we don't have enough documents for the public APIs.

https://waku.gg/blog/introducing-waku

@dai-shi dai-shi mentioned this issue Jan 17, 2024
Merged
@ojj1123
Copy link
Contributor

ojj1123 commented Jan 17, 2024

How about initializing git setting? (git init and then recomanded .gitignore, etc)
I think it's a bit low-priority but It seems like good to be at waku@v1.

@dai-shi dai-shi mentioned this issue Jan 17, 2024
Closed
@dai-shi
Copy link
Owner Author

dai-shi commented May 26, 2024

#24 (comment)

@tom-sherman Do you know any updates?
I guess it's unlikely that the React docs specify such details.

@tylersayshi
Copy link
Contributor

Explore Jotai integration

@dai-shi Is this still something that needs exploration?

If yes, what are some things that you'd be concerned about with using jotai + waku?

I suspect some exploration has been done already though, considering the waku.gg docs use example code with jotai as the state library.

@dai-shi
Copy link
Owner Author

dai-shi commented Jul 29, 2024

I suspect some exploration has been done already though, considering the waku.gg docs use example code with jotai as the state library.

The example in docs is what's possible now. What I would like to explore is to use atoms on the server too (that is connected to the client behind the scenes.) So, it's a very tight integration (and one reason that I started developing my own framework.)

I have a goal but don't have the implementation idea yet. #11 is an old attempt.

Anyway, there are so many things to do before working on it.

@dario-piotrowicz dario-piotrowicz mentioned this issue Aug 11, 2024
Closed
@sarat1669
Copy link
Contributor

@dai-shi does https://github.com/nksaraf/vinxi help with this roadmap?

@dai-shi
Copy link
Owner Author

dai-shi commented Sep 26, 2024

I don't believe so. Waku's design conflicts with Vinxi's design. So, it's unlikely that we use it at any time soon. We don't know the far future. Related discussion: #522

@ojj1123 ojj1123 mentioned this issue Oct 1, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@dai-shi @tom-sherman @sarat1669 @himself65 @zouhangwithsweet @tylersayshi @ojj1123 @Aslemammad @childrentime