You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
Activity
Taritsyn commentedon Jan 25, 2022
Hello, Dorez!
All other JS engines do not support this feature.
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 commentedon Jan 26, 2022
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.