-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Can you provide support for node v18? #354
Comments
I think this package does not use any latest node features. So it should work in node v18? And I am not very familiar with electron. I don't know how electron bundle your desktop app? @naria2/node does things like other native packages like esbuild, swc, that it includes different binary deps for different platform (see https://github.com/yjl9903/naria2/tree/main/packages/binary) Maybe I can republish it changing node version to v18? Or can you provide more information or minial reproduction for further debugging? |
I ran it independently and found that it didn't work with node v18, which is v18.16.0 index.js import { createClient } from "naria2";
import { createChildProcess } from "@naria2/node";
const client = await createClient(createChildProcess());
console.log(client.options); package.json {
"name": "test-naria2-node",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "node index.js"
},
"author": "",
"type": "module",
"license": "ISC",
"dependencies": {
"@naria2/node": "^0.0.24",
"naria2": "^0.0.24"
}
} |
Maybe it is related with the upstream library maria2. It does some polyfill to support different platforms. I find it terminates at this import |
I patch maria2 manually, could you try the latest 0.0.25? Related issue: hydrati/maria2#15 |
Unfortunately, the result is the same. My node version is v18.16.0 |
In my env, it works ok :(
|
This is my env, it looks like it should be a matter of operating system differences, mine is PC System:
OS: Windows 11 10.0.22621
CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
Memory: 39.48 GB / 63.76 GB
Binaries:
Node: 18.16.0 - ~\software\nodejs\node.EXE
Yarn: 1.22.19 - ~\software\nodejs\yarn.CMD
npm: 9.5.1 - ~\software\nodejs\npm.CMD
pnpm: 8.6.5 - ~\software\nodejs\pnpm.CMD
Browsers:
Edge: Chromium (120.0.2210.133)
Internet Explorer: 11.0.22621.1 |
Looks like it's not merging pr |
I have patched the package, so naria2 is not affected by the upstream. I am not sure whether patch works. Since that PR have merged, I will upgrade it tonight. |
I cloned the code, the local link was running successfully, but the download from npm still executed that part of the code, it seems that the patch is not fully effective |
I will upgrade naria2 after maria2 being published this Sat, for now you can do similiar patch in your project. |
When is the next release scheduled, since it's been a while :) |
For the upstream maria2 has not been updated... |
It should be resolved in hydrati/maria2@4947c12 and naria2 0.0.26 |
Clear and concise description of the problem
I'm using @naria2/node for my electron applications to automatically build the system version for cross-platform use. However, even the latest stable version of electron does not have node versions up to V20, and there are still many bugs to be fixed in 26, 27, and 28, so node V18 is still a very high share of electron applications. Is it possible to support @naria2/node over v18?
Suggested solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: