[DiceDB Console] Setup NextJS with Electron #69
Conversation
| @@ -0,0 +1,8 @@ | |||
| /** @type {import('postcss-load-config').Config} */ | |||
| const config = { | |||
| plugins: { | |||
There was a problem hiding this comment.
Hey, can we import tailwind config same way we did for playground? Would be better to have common tailwind base config
There was a problem hiding this comment.
I don't really understand tailwind yet, so not sure if this config will be enough to support theming. I have a separate task for this in our milestones
There was a problem hiding this comment.
Cool, I’ll do that since i set it up in playground too, will be faster
| "main": "main.js", | ||
| "type": "module", | ||
| "scripts": { | ||
| "dev": "concurrently --kill-others \"next dev -p ${PORT-4000}\" \"electron .\"", |
There was a problem hiding this comment.
Shouldnt we be running next from inside electron? How will this be packaged when we run the built version?
I think what we might is to use the standalone output of next and spawn it
There was a problem hiding this comment.
It makes sense to have standalone nextjs server running and electron app is pointing to it, for both local and packaged versions. There is no significant advantage from just shipping bundled files, not the server in packaged version.
Just one issue - users can run this directly also outside electron if they know the URL which shouldn't be an issue.
There was a problem hiding this comment.
I would prefer the server runs on the users system, and not us hosting it. Especially because we’ll actual servers if we wanna support load tests
There was a problem hiding this comment.
If you mean that the server for nextjs is gonna run in packaged version on the users system, what invokes it in the package version?
there is nothing calling next start
There was a problem hiding this comment.
Similar to forking a nodejs server, we can call childProcess.spawn('pnpm', ['start']) or something like that.
There was a problem hiding this comment.
Not sure that bundling pnpm in the final export is that good of an idea.
id rather just call node server.js on the bundled server output
There was a problem hiding this comment.
@KaviiSuri That was top of my head. There are so many ways to start node server, definitely we won't bundle pnpm in final build 😆
@KaviiSuri What is your idea of frontend in electron? |
I was thinking of mounting just the react app (so an SPA), but using nextjs allows us to use the server capabilities of nextjs directly without needing to write an express server. so we just use server functions or nextjs api routes for our server needs |
|
i think this is what you want to go towards here? https://www.saybackend.com/blog/03-electron-nextjs-ssr |
I haven't thought about using RSC. |
Its not about just rsc, its about using nextjs’s server capabilities, since they are very easy to use for frontend devs, so we dont need a express server. |
Build step will be handled while setting up publish flow as I have mentioned in milestones sheet. |
Summary
Not done in this PR