https://github.com/crutchcorn/nextjs-exe
Next.js running as a self-contained EXE?! Sure! Why not.
https://github.com/crutchcorn/nextjs-exe
Last synced: 4 months ago
JSON representation
Next.js running as a self-contained EXE?! Sure! Why not.
- Host: GitHub
- URL: https://github.com/crutchcorn/nextjs-exe
- Owner: crutchcorn
- Created: 2024-06-07T03:00:09.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-06-09T07:34:52.000Z (about 1 year ago)
- Last Synced: 2025-02-16T08:56:02.790Z (4 months ago)
- Language: JavaScript
- Homepage:
- Size: 1.05 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
# Next.js.exe
> **This is a bad idea that should not be used in production**.
This is a proof of concept for running the Next.js dev server as a single executable that contains all of the assets and code needed to run the server,
including RSC support.
## Architecture Diagram
> This isn't a great visual explainer. I wrote it quickly [while live on Twitch](https://twitch.tv/crutchcorn).
## Unfinished Warning
This project is _mostly_ finished but is not tested, as we are blocked by this issue:
https://github.com/nodejs/single-executable/issues/100
### Will it work?
I'm not sure, because our `fs` patch supposedly can read from `Buffer`s like `sea.getAsset` returns, however this **really heavily** expects
Next.js to not introspect the `dir` path as if it were a string in any way outside of using the `fs` APIs. I'm doubtful this is the case, but I could be wrong.