Evan Wallace

> have you considered also allowing a function to be passed with args (same as the callback) in case there was a case that required a little bit more logic?...

> which would still avoid unnecessary plugin calls if I'm not mistaken? The goal is to minimize the number of calls from Go into JavaScript since crossing this boundary is...

> What kind of decision decisions are you still evaluating? I'm also excited about plugins and looking forward to them being released. There are a few reasons why I haven't...

No updates at the moment. I have some stuff going on in my personal life that's taking priority right now (relocating some family members). My focus will be back on...

> My problem is whether is possible to rewrite the external module path Thanks for pointing this out. This was an oversight on my part. I updated the `plugins` branch...

> I want to get path to the index js in the output folder or it's contents in case I want to inline it. Thanks for raising this desire. This...

Sorry, I'm not sure I understand what you're trying to do anymore. It looks like the CSS can now depend on run-time values because of the use of `` `${button}`...

> Is it fair to assume that that branch will _eventually_ land in the main branch with approximately the current feature set intact? Yup. I'm actually working on this right...

> Maybe you could provide a "ignoreExternal" flag as part of the addResolver settings or provide external true/false as part of the args provided to the function? Yeah thanks for...

Getting the initial version of the plugin API out is going to be the focus of my next big release. One thing I'm worried about is the performance of the...