Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Considerations for choosing NodeBase instead of J2V8?

See original GitHub issue

This is a follow-up to https://github.com/staltz/react-native-node/issues/2

For my stackoverflow question on 4 possible solutions, I receive an answer from the NodeBase creator, basically stating that his project is a ‘plaything’ and J2V8 the best approach.

To me J2V8 (created by @irbull) looks like the most stable implementation currently, leading to my question: Why did you opt for NodeBase?

It seems to me with J2V8 you’d gain:

a much more active project
support for newer Node versions (currently 7.6.0, but 8.x just PR’ed)
additional features:
- 2-way js-to-java bridge (call java from script and vice versa)
- 2-way integrated error / exception handling
- chrome debugging support
- full build environment with docker-based cross-compile for unix, mac, windows and android
- more smaller stuff …

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

staltzcommented, Aug 3, 2017

Why did you opt for NodeBase?

Because it solved my problem.

support for newer Node versions (currently 7.6.0, but 8.x just PR’ed)

Actually we can do a lot even with older versions of node.js. Note that Node v6 is currently the LTS.

a much more active project

See above.

2-way js-to-java bridge (call java from script and vice versa)

We don’t need this

2-way integrated error / exception handling

We can get errors into the adb logcat, that seems enough to me.

chrome debugging support

That would be nice.

0reactions

teaserbotcommented, Sep 14, 2017

like https://github.com/eclipsesource/J2V8/issues/335 also you project lead? or @irbull

Top Results From Across the Web

Ideas for J2V8 project improvement · Issue #335 · eclipsesource ...

This issue is a discussion thread for J2V8 project improvement and is ... Considerations for choosing NodeBase instead of J2V8? staltz/react-native-node#3.

Viable options for running NodeJS on Android (Aug 2017)

1. Running V8 javascript engine which includes NodeJS (J2V8) · Specify the versions to compile in build_system/build_settings.py · Start a build ...

J2V8 - EclipseSource

J2V8 is a set of Java bindings for Google's popular JavaScript engine, V8. ... In this tutorial we will demonstrate how to execute...

Run a separate Node.js process behind a React Native app

Run a real Node.js process in the background, behind a React Native app. DEPRECATED. Please use Node.js Mobile by Janea Systems instead. It...