Importing modules from relative paths fails for js/ts cells. Likely also for other languages.

[seldomU]

This no longer works in Runner v2 but does in v1.

A typescript cell like this will fail, even with the imported file existing in the same directory as the runme file:

import foo from './bar.ts'

bar.ts source:

export default function() { console.log("hello!") }

The same issue should affect other languages for which runme creates a temporary file of the cell source code in a different directory.

Setting the cwd option does not help, because import paths are interpreted as relative to the source file location, not relative to the working directory.

A solution would be to create the temp file in the same directory as the runme file, or to turn that choice into a configuration option.

Alternatively, the cell content could be passed as a string to deno eval or node -e, which should run it as a temp file in the original directory.

[sourishkrout]

Weird, it seems to work as expect for me.

You are using the notebook UI right @seldomU?

[seldomU]

Yes @sourishkrout, I'm using the vs code extension and execute the cell via the notebook UI. The error message for my example typescript cell looks like this:

error: Module not found "file:///tmp/runme-3757777008/bar.ts".
    at file:///tmp/runme-3757777008/runme-script-1476611870.ts:1:17

[sourishkrout]

What OS are you running on specifically, @seldomU?

[seldomU]

It's Ubuntu 24.04 and the runme extension is latest (v.3.15.5)

[seldomU]

@sourishkrout I tried it on a second machine and it works fine there. Same OS and extension version.

I double checked where the cell code is executed on the second machine with console.log(import.meta.dirname) and got the correct (original) directory.

Can the vscode version make a difference? I can compare that later today.

[seldomU]

@sourishkrout I got it working by removing this line from my vscode settings.json:

"runme.server.runnerVersion": "v2"

I don't know how it's related, but now the temp file is created in the original directory.

[sourishkrout]

Hi @seldomU, that was my next question. Glad you found the culprit. Sounds like this unblocks you?

Runner v2 is a rewrite of the extension's execution that closes gaps with Unix pipes/stdio. Improvements that are more important to the CLI, however, we haven't fully completed the migration yet.

I'm considering this a bug in Runner v2. Let's leave this issue open and I'll update the description. Thanks for your help!

PS: You can see what Runner is being used by dropping echo $RUNME_RUNNER into a shell cell.

[seldomU]

@sourishkrout yes that unblocks me. Thank you for the explanation.