Dmitry Volyntsev

Hi @s3rj1k, I doubt that we will implement synchronous version of ngx.fetch(). Instead please share your use case so we will think on how to use async ngx.fetch() there. You...

@s3rj1k Please, elaborate more, what header and what information you send to an external service. One possible workaround is to use r.subrequest() for the main request, modify the subrequest response...

Hi @s3rj1k, no progress on my side. Also, `ngx.fetch()` is a part of nginx module (ie is tightly integrated with nginx and will not work without nginx). So it will...

Hi @baiyuxiong, There is no way to separate njs logs and nginx error logs as of now. One way to separate them is to filter the error.log file as `grep...

Hi @radsoc, Thank you for the feedback and for letting us know that NJS is preferred. Let me address some of your questions. > Performance is key; full ES spec...

@lancedockins Thank you for the feedback. First of all at this moment we do not plan to retire njs engine. >What is NJS doing to speed up context instantiation to...

Hi @lancedockins, The items 3 is certainly a possibility. There is a trade-off between: * having persistent memory which quite often is desired. * having a clean environment for each...

Hi @s3rj1k, The plan is to introduce QuickJS as a drop-in replacement for NJS engine. So most of the existing scripts and configurations should work with the new engine. To...

Hi @bnoordhuis, We do not have specific plans yet, but given current circumstances with the stalled development, I think we will have to migrate to the [quickjs-ng](https://github.com/quickjs-ng/quickjs) in the near-term...

Hi @angelomandato, Thank you for the feedback, it is helpful. This is right place to send your feedback. > If you can run node apps then that is a game...