You can set the templates directory to anything in plugin.json, I think it defaults to just templates if you don't specify.
Them you match the path from views, so it would be templates/emails where you put them.
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.