Custom node flags when launching JSReport via windows service

[zhwatts]

Hello, I'd like to increase the available memory to the Node service used by JS-report. Typically, I'd do something like this

NODE_OPTIONS=--max-old-space-size=6096 << further validated via this link: Long Reports

In my instance, I am running JS Report on Windows, and have the JS-Report Windows service installed. What's the best practice recommendation for getting the Windows Service to start with the custom NODE_OPTIONS flag?

I'm experimenting with something like this:
sc config jsreport-server binPath= "<path_to_node_executable> <path_to_jsreport_script> <custom_flags>"

[jan_blaha]

I don't have a lot of experience with windows services..
However, have you tried using environment variables like described here
https://serverfault.com/a/1103091