Julian Goacher

@vybs Thanks Veena, but isn't tap synchronous? I agree that it's reasonable to expect the writer of a helper function to resolve the values using tap/capture etc. but the point...

@vybs partials with params resolving to async values don't seem to work. I haven't delved into the code to work out exactly what's happening, and this is probably a separated...

@vybs Scratch that, I'd forgot to call end() on the n2 handler. It does actually work, I'll look deeper into the code later.

chunk.partial just pushes its params onto the stack before evaluating the partial template, so ultimately the param values are resolved using the standard var substitution mechanism, which is a different...

The problem with my first attempt to read multiple params was that end() wasn't called after chunk.capture(); code that actually works looks like this: ``` js { "bar": "fubar", "helper":...

@rragan I'm not sure about that. The tap helper is a broken implementation because it doesn't support asynchronous value resolution. Probably doesn't cause problems for a lot of use cases...

I've posted a gist with a working helper wrapper function: https://gist.github.com/innerfunction/6252243

I'm coding in a node.js environment where pretty much everything is asynchronous, and I think that in this case it would make sense for the conversion to be automatically be...

@carchrae You're welcome - yep, I'm still using it.

I came across this problem when setting up a react-admin auth provider and had to do the following to fix: * Set `"module": "es2022"` and `"moduleResolution": "bundler"` in ts settings...