Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / JeringTech/Javascript.NodeJS issues and pull requests

#176 - Next.JS instead of Node.js

Issue - State: open - Opened by LorenDorez about 1 year ago

#175 - Facing issue with Jering.Javascript.NodeJS

Issue - State: open - Opened by ganesh328916 about 1 year ago - 2 comments

#174 - Has anyone used this with React/JSX?

Issue - State: open - Opened by michaelmarziani about 1 year ago

#173 - Use ESM instead of CJS. Potentially fixes #160

Pull Request - State: closed - Opened by aKzenT about 1 year ago - 2 comments

#172 - Unit test fixes

Pull Request - State: closed - Opened by aKzenT about 1 year ago - 1 comment

#171 - Vite + ESM

Pull Request - State: closed - Opened by thebuilder about 1 year ago - 1 comment

#170 - Call the same instance?

Issue - State: open - Opened by cinderblockgames over 1 year ago

#169 - Which port does this nuget use to communicate with Node.Js ?

Issue - State: closed - Opened by liaosunny123 over 1 year ago - 2 comments

#168 - InvocationException: Worker is not defined

Issue - State: closed - Opened by GabrielePicco over 1 year ago - 5 comments

#167 - Fix extra file watcher events causing unnecessary Node.js restarts

Pull Request - State: closed - Opened by JeremyTCD over 1 year ago

#166 - Handle process outputs correctly. Fixes #165

Pull Request - State: closed - Opened by aKzenT over 1 year ago - 1 comment

#165 - StandardOut and StandardError are not properly read

Issue - State: closed - Opened by aKzenT over 1 year ago

#164 - Jering.Javascript.NodeJS.InvocationException in Production

Issue - State: closed - Opened by YSR007-IND over 1 year ago - 6 comments

#163 - How to pass stdio to nodejs

Issue - State: open - Opened by soroshsabz over 1 year ago - 11 comments

#162 - Obtaining console.log output from executed script

Issue - State: open - Opened by dannyhaak over 1 year ago - 3 comments

#161 - Add test case for issue #160

Pull Request - State: open - Opened by aKzenT over 1 year ago

#160 - ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING error when using ESM script to render

Issue - State: closed - Opened by aKzenT over 1 year ago - 20 comments

#159 - Is it possible to return a stream from nodejs?

Issue - State: closed - Opened by burner03 over 1 year ago - 2 comments

#158 - Multiple function return values at different times

Issue - State: open - Opened by leumasme over 1 year ago - 1 comment

#157 - Allow HttpResponseMessage in invoke result, and response control in c…

Pull Request - State: closed - Opened by DaniilSokolyuk over 1 year ago - 3 comments

#156 - Added release 7.0.0-beta.2.

Pull Request - State: closed - Opened by JeremyTCD over 1 year ago

#155 - Changes to NodeJSProcess

Pull Request - State: closed - Opened by JeremyTCD over 1 year ago

#154 - Add support for mjs.

Pull Request - State: closed - Opened by JeremyTCD over 1 year ago

#153 - Upkeep

Pull Request - State: closed - Opened by JeremyTCD over 1 year ago

#152 - System.ObjectDisposedException: The semaphore has been disposed.

Issue - State: closed - Opened by aKzenT almost 2 years ago - 1 comment

#151 - Support for ES Modules

Issue - State: closed - Opened by thebuilder almost 2 years ago - 3 comments

#150 - Cache control?

Issue - State: closed - Opened by toiyabe almost 2 years ago - 2 comments

#149 - How to call Node JS script and possibly with parameter from WinForms App?

Issue - State: closed - Opened by zydjohnHotmail almost 2 years ago - 2 comments

#147 - Is there a option to use import/export syntax?

Issue - State: closed - Opened by entropin about 2 years ago - 3 comments

#145 - Node startup fails on Azure App Service

Issue - State: closed - Opened by aKzenT about 2 years ago - 3 comments

#144 - Improve process connection system

Pull Request - State: closed - Opened by JeremyTCD about 2 years ago

#141 - InvokeFromStringAsync can't find module exports assignment...

Issue - State: closed - Opened by Jerrill about 2 years ago - 7 comments

#140 - Apparent hang using the cached code

Issue - State: closed - Opened by highfield about 2 years ago - 5 comments

#139 - JsCompilationException on spawn identifier

Issue - State: closed - Opened by soroshsabz about 2 years ago - 3 comments

#138 - Event Listener on nodejs

Issue - State: closed - Opened by duduccosta about 2 years ago - 1 comment

#137 - javascript中转换Number有类型处理不当的问题。

Issue - State: closed - Opened by silmooninc over 2 years ago - 2 comments

#136 - Add ability to provide a JSON date parser

Issue - State: closed - Opened by mattchidley over 2 years ago - 4 comments

#135 - Added check for NumRetries = 0

Pull Request - State: closed - Opened by johnrom over 2 years ago - 1 comment

#134 - Infinite Loop when using ProcessRetries.

Issue - State: closed - Opened by johnrom over 2 years ago - 8 comments

#133 - Sandbox execution of javascript

Issue - State: closed - Opened by honibis over 2 years ago - 2 comments

#132 - Proxy

Issue - State: open - Opened by gligi over 2 years ago - 4 comments

#131 - JS is not backwards compatible

Issue - State: closed - Opened by johnrom over 2 years ago - 3 comments

#130 - I want to subscribe to events

Issue - State: closed - Opened by hbdbim over 2 years ago - 5 comments

#129 - JS Logging

Issue - State: closed - Opened by zpxp over 2 years ago - 2 comments

#128 - Updated precompiler directives to support .net 5 and above

Pull Request - State: closed - Opened by samcic almost 3 years ago - 1 comment

#127 - Update preprocessor directives to use NET5_0_OR_GREATER to support .net 6

Issue - State: closed - Opened by samcic almost 3 years ago - 1 comment

#126 - Does it support highlight.js

Issue - State: closed - Opened by LittleNewton almost 3 years ago - 8 comments

#125 - node.js process not properly disposed after timeout is hit

Issue - State: closed - Opened by ulieckstein almost 3 years ago - 1 comment

#124 - Additions and changes to retries

Pull Request - State: closed - Opened by JeremyTCD almost 3 years ago

#123 - In version 6.X, state is lost after an exception is thrown

Issue - State: closed - Opened by Taritsyn almost 3 years ago - 4 comments

#122 - Add move to new process

Pull Request - State: closed - Opened by JeremyTCD almost 3 years ago

#121 - Add a method to manually invalidate the cached script

Issue - State: closed - Opened by highfield almost 3 years ago - 5 comments

#120 - Security concern: Is the node process isolated from the file system or network?

Issue - State: closed - Opened by panospd almost 3 years ago - 6 comments

#119 - How to deploy a project with local node_modules?

Issue - State: closed - Opened by cosmoKenney almost 3 years ago - 3 comments

#118 - Error Json Value cannot be converted to byte[]

Issue - State: closed - Opened by aboah almost 3 years ago - 2 comments

#117 - Connection Exception when running on Azure App Service

Issue - State: closed - Opened by hallojoe about 3 years ago - 2 comments

#115 - Jering.Javascript.NodeJS.ConnectionException on Azure App Service

Issue - State: closed - Opened by heinzmuller over 3 years ago - 7 comments

#114 - How to debug JavaScript when using Jering.Javascript.NodeJS (Fetch-Post)

Issue - State: closed - Opened by zydjohnHotmail over 3 years ago - 5 comments

#112 - PhysicalFileProvider.Root and file not found issues in production build

Issue - State: closed - Opened by princefishthrower over 3 years ago - 2 comments

#111 - NPM dependencies

Issue - State: closed - Opened by marceln over 3 years ago - 2 comments

#110 - Fix invocation exception message

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago

#109 - Error message has newline (\n) character in it?

Issue - State: closed - Opened by princefishthrower over 3 years ago - 4 comments

#108 - Release 6.0.0

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago

#107 - Error installing latest stable version

Issue - State: closed - Opened by markzolotoy over 3 years ago - 4 comments
Labels: question

#106 - Add executable path option

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago - 1 comment

#105 - Ability to configure node runtime

Issue - State: closed - Opened by Rob-Read over 3 years ago - 3 comments
Labels: enhancement

#104 - Is it possible to invoke C# methods from javasript with Javascript.NodeJS?

Issue - State: closed - Opened by smilovich over 3 years ago - 1 comment

#103 - Can I use chrome-remote-interface with Jering.Javascript.NodeJS?

Issue - State: closed - Opened by zydjohnHotmail over 3 years ago - 3 comments

#102 - 6.0.0 Things To Do

Issue - State: closed - Opened by JeremyTCD over 3 years ago
Labels: help wanted, good first issue

#101 - Improve robustness

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago - 1 comment

#100 - Fix http 2 for .Net 5.0

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago - 1 comment

#99 - Failed to connect to NodeJS. Refer to the inner exception for details.

Issue - State: closed - Opened by markzolotoy over 3 years ago - 3 comments
Labels: question

#98 - Relative path for InvokeFromFileAsync

Issue - State: closed - Opened by markzolotoy over 3 years ago - 6 comments
Labels: question

#97 - Switch to http 2

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago - 1 comment

#95 - Sending parameters

Issue - State: closed - Opened by markzolotoy over 3 years ago - 9 comments
Labels: question

#94 - Error: Cannot find module 'xmldom'

Issue - State: closed - Opened by jefersonmlopes over 3 years ago - 2 comments
Labels: question

#93 - Prevent console window

Pull Request - State: closed - Opened by JeremyTCD over 3 years ago - 1 comment

#92 - Removing NodeJS Console Window

Issue - State: closed - Opened by hansooms999 over 3 years ago - 7 comments
Labels: bug

#91 - Received a HTTP response with an unexpected status code: ServiceUnavailable

Issue - State: closed - Opened by villelaitila almost 4 years ago - 2 comments
Labels: question

#90 - Fix incompatibilities with newer node versions.

Pull Request - State: closed - Opened by JeremyTCD about 4 years ago - 1 comment
Labels: bug

#89 - Issue running with node 13/14

Issue - State: closed - Opened by giuliano-barberi-tf about 4 years ago - 3 comments
Labels: bug

#88 - Added CatchUncaughtUserErrors flag.

Pull Request - State: closed - Opened by JeremyTCD about 4 years ago - 2 comments
Labels: enhancement

#87 - Fix minor typos

Pull Request - State: closed - Opened by flcdrg about 4 years ago - 2 comments

#86 - Co-debug and JavaScript exception handling

Issue - State: closed - Opened by markm77 about 4 years ago - 13 comments
Labels: enhancement

#85 - disable keep alive timeout, headers timeout and log any server timeouts

Pull Request - State: closed - Opened by blushingpenguin over 4 years ago - 3 comments
Labels: bug

#84 - capture the final output from node processes to help diagnose unexpected node exits

Pull Request - State: closed - Opened by blushingpenguin over 4 years ago - 4 comments
Labels: bug

#83 - Differences with microsoft/ClearScript

Issue - State: closed - Opened by faramos over 4 years ago - 2 comments
Labels: question

#82 - Question: Example to replace aspnet-prerendering in asp.net core 3.1?

Issue - State: closed - Opened by christopherpross over 4 years ago - 2 comments
Labels: question

#81 - Question about concurrency of multiple independent caller processes

Issue - State: closed - Opened by Edza over 4 years ago - 3 comments
Labels: question

#80 - An existing connection was forcibly closed by the remote host.

Issue - State: closed - Opened by Edza over 4 years ago - 7 comments
Labels: question

#79 - Deep argument serialization

Issue - State: closed - Opened by Edza over 4 years ago - 9 comments
Labels: question

#78 - Documentation question

Issue - State: closed - Opened by abusalaa7 over 4 years ago - 2 comments
Labels: documentation

#77 - Exit if parent process dies

Issue - State: closed - Opened by dustinsoftware over 4 years ago - 2 comments
Labels: question