Skip to content
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

Question, are you compiling and including all of nodejs? #20

Open
pauldotknopf opened this issue Sep 22, 2016 · 9 comments
Open

Question, are you compiling and including all of nodejs? #20

pauldotknopf opened this issue Sep 22, 2016 · 9 comments

Comments

@pauldotknopf
Copy link

Are you compiling all of nodejs, but only exporting the V8 functions you need?

The reason why I ask is because I think this could potential allow running javascript code in .NET that actually utilize network/file and node_modules.

@prepare
Copy link
Owner

prepare commented Sep 23, 2016

Yes

:)

@prepare
Copy link
Owner

prepare commented Sep 23, 2016

The reason why I ask is because I think this could potential allow running javascript code in .NET that actually utilize network/file and node_modules.

👍
I 've test it, it works!

@pauldotknopf
Copy link
Author

Wait, this is already a feature?

There is a JavaScript thread loop implemented in here?

I heard node was hard to embed, leading electron to for it.

https://github.com/electron/node

It wasn't hard for you? Or, are you using their fork?

@prepare
Copy link
Owner

prepare commented Sep 23, 2016

Are you compiling all of nodejs, but only exporting the V8 functions you need?

In this Espresso repo,
we use v8 from nodejs,

but It not include any function from node directly

because I want to use it with our HtmlRenderer project.
so I want to show how to interface with the project,
and make sure that no nodejs code/functions are on client platform.

so I export only V8 functions from nodejs + our some functions that control it.


Wait, this is already a feature? There is a JavaScript thread loop implemented in here?

Yes, but It's not in public repo , it will be release later soon.


It wasn't hard for you?

In my experience (not much like electron dev team) + my context,
not hard, it's easy,
we use the same technique like we use with V8.

@prepare
Copy link
Owner

prepare commented Sep 23, 2016

are you using their fork?

No, I use the original nodejs code.
:)

@enginekit
Copy link

enginekit commented Oct 10, 2016

hello @pauldotknopf,

Today, I have sent the special version of Espresso.
It is "EspressoCup". The NodeJS + Espresso Extension.
see detail more at

https://github.com/CompilerKit/Espresso/wiki/Build-NodeJS-for-Espresso-Cup

@pauldotknopf
Copy link
Author

Amazing!

I know the API is different than EdgeJS, but how do you see this library, compared to it?

Also, is this repo your working fork? Is the CompilerKit one the home?

@enginekit
Copy link

enginekit commented Oct 10, 2016

@pauldotknopf
I love the simplicity and flexibility of this lib.

(the detail in https://github.com/CompilerKit/Espresso/wiki/Build-NodeJS-for-Espresso-Cup
shows that just 8 patches to original NodeJS code,
the Espresso becomes EspressoCup)

I think, the Espresso is a little lib that answers my requests.
I can't compare it EdgeJS ;) , (EdgeJS is a greate lib)

CompilerKit/Espresso is my fork.
I contribute back to @prepare /Espresso

@prepare
Copy link
Owner

prepare commented Jun 8, 2017

Now Espresso (V8/ NodeJS 7.10.0+) can run on .netcore/.netstandard on macOS, Linux and Windows.
see => #30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants