||3 years ago|
|deps||3 years ago|
|node@a3a9e31c32||3 years ago|
|src||3 years ago|
|.gitignore||4 years ago|
|.gitmodules||4 years ago|
|LICENSE||4 years ago|
|README.md||4 years ago|
|azure-pipelines-template.yml||3 years ago|
|azure-pipelines.yml||3 years ago|
|build.js||3 years ago|
|common.gypi||3 years ago|
|test.js||4 years ago|
|yode.gyp||3 years ago|
Yode is a fork of Node.js that replaces its event loop with GUI message loop, it is designed to be used together with the Yue library.
Changes to Node.js
- The event loop is replaced with native GUI message loops:
- On Linux it is
- On macOS it is
- On Windows it is
- On Linux it is
- When the executable is appended with ASAR archive, Yode will try to start with with app inside the archive.
- The process will not automatically quit when there is no work, you have to call the native APIs to quit the GUI message loop.
- The process will quit when BOTH the GUI message loop and Node.js event loop have quit. So if there are still Node.js requests pending, the process will wait until all of them have finished.
- There is a new
process.stdinis not supposed to work.
- On Windows the executable uses
WINDOWSsubsystem instead of
CONSOLEsubsystem, so unlike Node.js there is no console attached and REPL won't work.
The prebuilt binaries can be found in the Releases page, modules installed by
npm can be used directly in Yode.
To package your Node.js project with Yode, you should use yackage.
Note that it is strong recommended to install the official Node.js with the
same version of Yode, otherwise native modules installed by
npm may not work
correctly in Yode.
$ node ./build.js [x64|ia32]
The MIT license.