Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"nodejs not available" - how does ts-worksheet determine that? #9

Open
niieani opened this issue Nov 17, 2024 · 3 comments
Open

"nodejs not available" - how does ts-worksheet determine that? #9

niieani opened this issue Nov 17, 2024 · 3 comments

Comments

@niieani
Copy link

niieani commented Nov 17, 2024

Hi!

I have node installed via proto, and available in my PATH. But the extension cannot find it.
I've also tried installing it via brew install nodejs, but that didn't help.
Finally, I also added a symlink to node at /usr/local/bin/node, but still no luck.

Where does ts-worksheet attempt to find node? It would be great if the path were configurable, or if it attempted to use the system PATH based on user's configured shell RC file (e.g. ~/zshrc).

Cheers!

@mearleycf
Copy link

I haven't done any of the trial and error that @niieani has done, but I'm having the same issue. It only shows Deno as available. However, if I use Deno, the extension doesn't actually do anything.

Here is a picture at least--note the file on both sides of the split is the same file, types.ts. On the right, at the top of the file, you see the // ts-worksheet-with-variables command. On the left, you see where I've added a single //? to a type. On the far left you can see I've selected Deno because it's the only option available.

CleanShot 2024-12-19 at 09 08 30

@chwoerz
Copy link
Contributor

chwoerz commented Dec 26, 2024

What gets printed when you run "which node" in the terminal?

@niieani
Copy link
Author

niieani commented Dec 26, 2024

I've tried with both proto enabled and disabled in my .zshrc:

❯ which node
$HOME/.proto/shims/node
❯ which node
/usr/local/bin/node

In either of these cases the extension says "nodejs not available".

FYI

❯ node -v
v22.11.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants