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

Node Stream #100

Open
LorenDorez opened this issue Jan 24, 2022 · 2 comments
Open

Node Stream #100

LorenDorez opened this issue Jan 24, 2022 · 2 comments

Comments

@LorenDorez
Copy link

So the Node Engine implementation for javascript.Nodejs supports returning a stream from node to .net by setting the return type to Stream. However, JES has a validation helper that check to make sure the return type is valid and stream is not one of them.

Is there a reason or can we look to see about allowing this?

@Taritsyn
Copy link
Owner

Hello, Dorez!

So the Node Engine implementation for javascript.Nodejs supports returning a stream from node to .net by setting the return type to Stream.

All other JS engines do not support this feature.

However, JES has a validation helper that check to make sure the return type is valid and stream is not one of them.

This is how it is intended, because the JavaScript Engine Switcher library determines unified interface for access to the basic features of popular JS engines.

Perhaps you should use the Jering.Javascript.NodeJS library directly.

@LorenDorez
Copy link
Author

Thanks for the reply and info. I can see where it would be out of scope for this project. I'll look to mock something up.

I just want to experiment with in junction with ReactJS.net using the new render stream to support lazy on ssr in react v18.

Thanks for a great project btw.

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

2 participants