Wow! So turns out it was a silly error on my part. I had tried the Error object previously, but it was while looking at a different part of the code... I was actually looking/changing the 'imagekit' case in the code and being stumped as to why I was still seeing the behavior as I explained. Anyhow, it is working as it should when passing in an Error object. Thanks for the extra insight!
grunt "ad-hoc compilation" for multiple instance installation?
-
Re: Plugin development 2021 updated - environment and dev workflow - request
I noticed grunt only working with a single instance (port number). I tried swapping in the multiple-instance target with no luck. Is there an easy way to "upgrade" grunt to make it work with multiple instances?
-
I understand wanting to have as close to production as possible but I don't think running multiple instances is ever useful when working on the client side. I can't think of any cases where multiple instances would make a difference for client-side code.
Restarting the server could be useful but you don't gain much from grunt there.
-
@pitaj It's an issue of preference I guess. I'd like to avoid grunt being a dev tool forcing me to deviate from my integrations needs. If grunt would support multiple instances, it would be great and I'd use it. Else I'd stick with the current big hammer method of always recompiling unconditionally and restarting nodebb afterwards. Accepting the additional penalty of nginx rev proxy streaming timeouts. Not elegant but it works.
