now dev failed to find deno exacutable when deno is installed via asdf

[kt3k]

If I installed deno via asdf, now dev doesn't seem working with the following error:

$ npx now dev
Now CLI 17.0.3 dev (beta) — https://zeit.co/feedback
> Creating initial build
> Success! Build completed
> Ready! Available at http://localhost:3000
unknown command: deno. Perhaps you have to reshim?
unknown command: deno. Perhaps you have to reshim?
error: bad deno executable
Unexpected bootstrap error when calling AWS_LAMBDA_RUNTIME_API /init/error:
InitException: bad deno executable
    at Lambda.<anonymous> (/Users/kt3k/s/now-deno-example/node_modules/now/dist/index.js:2:3545645)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/kt3k/s/now-deno-example/node_modules/now/dist/index.js:2:3543532)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

If I removed asdf-installed deno and installed it with the official installer script, then it worked. Maybe this isn't a issue of this tool, but do you have any idea about the cause of the above error? @lucacasonato

[lucacasonato]

The error means that deno can't be found in your path. When you install deno via asdf, can you run it yourself from the terminal you are running now dev from?

[kt3k]

Yes, I can use deno under ~/.asdf/shims/ in the terminal and now dev from the same terminal seems failing to find it.

MacBook-Pro-4:now-deno-example kt3k$ which deno
/Users/kt3k/.asdf/shims/deno
MacBook-Pro-4:now-deno-example kt3k$ deno --version
deno 0.32.0
v8 8.1.108
typescript 3.7.2
MacBook-Pro-4:now-deno-example kt3k$ now dev
Now CLI 17.0.3 dev (beta) — https://zeit.co/feedback
> Creating initial build
> Success! Build completed
> Ready! Available at http://localhost:3000
unknown command: deno. Perhaps you have to reshim?
unknown command: deno. Perhaps you have to reshim?
error: bad deno executable
Unexpected bootstrap error when calling AWS_LAMBDA_RUNTIME_API /init/error:
InitException: bad deno executable
    at Lambda.<anonymous> (/Users/kt3k/.asdf/installs/nodejs/12.13.0/.npm/lib/node_modules/now/dist/index.js:2:3545645)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/kt3k/.asdf/installs/nodejs/12.13.0/.npm/lib/node_modules/now/dist/index.js:2:3543532)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

(Could be an issue of asdf...)

[lucacasonato]

Interesting... internally I call which deno and then create a symlink from [project root]/.now/builders/now-deno/[entry file path]/layer/bin/deno to the deno executable I found with which deno. I don't know if asdf just doesn't like its shims being symlinked. Can you check if there is a symlink at [project root]/.now/builders/now-deno/[entry file path]/layer/bin/deno and if you can run it? That might give some more insight.