Osama Abbas comments

Results 46 comments of


                                            Osama Abbas

Unable to get correct exit code from process.exit(code) when using bytenode to compile

This is because, in the case of bytenode, you get the exit code of bytenode process itself. The use of `spawnSync` in bytenode CLI needs to be corrected to capture...

Unable to get correct exit code from process.exit(code) when using bytenode to compile

Let me know if this workaround solves your issue. I'm a bit busy so I won't work on this fix unless necessary.

Electron path in 1.3.5 doesn't exist

I guess the problem is because your electron is locally installed and you are trying to use the globally-installed bytenode. With the latest change, (global) bytenode will look for the...

Electron path in 1.3.5 doesn't exist

If both are installed locally, then I cannot reproduce your issue. If you can create a minimal setup that shows the error, then we can look into it.

Electron path in 1.3.5 doesn't exist

No worries, take your time.

improvement(index): remove global object and support edit extension name

Thank you for this improvement. Removing the global object will break using bytenode repl. So let me think if we can fix this in a cleaner way. Otherwise, I think...

Folder with .js in the name breaks compilation

> I've tried to run `bytenode --compile ./**/*.js` against node_modules, however, it failed with > > > Error: Cannot find file '/home/toshiba/open-source/node-hello/node_modules/ipaddr.js' > > I've ran `npm i express` to...

Cannot change --max-old-space-size

This should work: ``` node --max-old-space-size=7500 -r bytenode test.jsc ``` Given that `bytenode` is installed locally.

Cannot change --max-old-space-size

This bug should be fixed in `cli.js`. Thank you for reporting.

Dependency resolving problem with compiled byte code

Could you please provide a complete minimal example that shows the problem with a simple `npm install && npm run`? Also, try running the project like this: `node -r bytenode...