rightaway
rightaway
That's right. Both exec and run are failing. Other things seem to work alright, though I haven't tested much of yet but will be doing so. Btw what exactly is...
With regards to npm run/exec not working with system, is there any workaround I can use now that would let me access the system node while I'm in a folder...
Also would there any difference in how to configure `caw` when using an HTTPS proxy to access an HTTP webpage vs an HTTPS webpage? Thank you!
So when accessing an HTTPS page, should it be like `caw('https://1.2.3.4:555', {protocol: 'https'})`? So `https` in both places, the proxy string as well as the `protocol` value?
And when accessing a regular HTTP page, it's `caw('http://1.2.3.4:555', {protocol: 'http'})`, so `http` in both places instead of `https`?
koa-tree-router is already taking `ctx.request.url` and looking through all routes to determine which one matches. If you could expose that function so we could call it ourselves, koa-tree-router middleware will...
Something like `router.getMatchedPattern(ctx)`, which uses `ctx.request.url` like `/route/1` and returns the actual pattern that was matched, like `/route/:param`.
@dosentmatter That's duplication as well. If you change `/path` it has to always be done in 2 places. Plus giving us the ability to call a generic function like I've...
As a workaround not a solution I understand.
@leafac Looking forward to this so that switching from `pkg` is possible. Does this issue need https://github.com/nodejs/node/issues/35711 to be added first?