obsidian-execute-code: Typescript Not Working

If you need a quick fix, copy and paste the output of which node into ts-node path followed by the output of which ts-node. They both need to be in the ts-node path field and the arguments field should be left blank.

The problem is that the shell environment executing the provided commands isn’t loading the local .zshrc or .bashrc. It also only includes bin, /usr/bin, and /usr/sbin. These folders are protected by MacOS and, by default, should not be written to even if it’s just for the purpose of adding symlinks.

It would be much better if we could ensure that /usr/local/bin gets added to the shell environment before commands are executed.

@skdamico I haven’t looked through all of the code yet to see how the ts executor is being formed, but I assume that somewhere along the road, a child process is forked off that executes the provided commands. If that’s correct, then the child process only has access to the environmental variables within the scope of the Obsidian process, which isn’t much.

You would need to do one of two things. Either, you would need to source select rc, env, or profile files before executing the provided command or add additional directories to the path yourself. I would recommend the latter.

You would need an input field to accept additional directories, such as what the Shell Commands plugin uses https://publish.obsidian.md/shellcommands/Environments/Additions+to+the+PATH+environment+variable

You would need to concatenate those with the PATH variable and pass that into the child process, the child process would need the additional argument { env: dirs.join(":") + ":" + process.env.PATH }. You would of course need to ensure that some dir is provided, otherwise, you wouldn’t pass this argument at all.

This would at least allow users to specify which directories they want included in their PATH. For most UNIX users, adding /usr/local/bin would be enough but others may also want to include their homebrew dir, etc.

The problem is that the shell environment executing the provided commands isn’t loading the local .zshrc or .bashrc. It also only includes bin, /usr/bin, and /usr/sbin. These folders are protected by MacOS and, by default, should not be written to even if it’s just for the purpose of adding symlinks.

@isr413 Do you know how we can make sure that the .*shrc files are loaded?

https://unix.stackexchange.com/questions/71253/what-should-shouldnt-go-in-zshenv-zshrc-zlogin-zprofile-zlogout

Suggest everyone to read the top two answers to this StackExchange. But TL;DR: .zshrc is for interactive shells and is read once per shell creation .zshenv is for applications, etc and is read every time. export your $PATH, $EDITOR, other application level vars here.

ts-node calls the same version of node which was used to run it. Now that which node works, could you try node for the path and /path/to/ts-node for the first argument? e.g:

There already were a few issues by people using the combination MaxOS + Homebrew. We don’t have a general solution yet but we there seems to be a common problem.