Does it work with nodejs express, fastify ...?

[wallabyjs]

Does it work with nodejs express, fastify ...?

[ArtemGovorov]

There's a plan to make it work with application launched directly as node file_name.js.

[jaydeepkarena]

Yes, i am looking for the same.

[patroza]

There's a plan to make it work with application launched directly as node file_name.js.

this would be great. having it all centrally integrated with the editor is a cool unified experience.

[ArtemGovorov]

@patroza We are working on it, however no ETA to share yet.

[NikGovorov]

Hi guys,

Today, we are happy to announce the release of support for node app.js-like workflows. Please refer to Universal Node applications section of our docs for more information.

[tarwich]

Thanks for the response! Updating the docs would help!

I don't like tools to touch my .profile without permission. Plus I am using fishshell, so it wouldn't have helped. I switched to bash for troubleshooting purposes. It would be nice if this were a setting, or something (even if it were defaulted to true). Perhaps instead of a setting, a command? I'll let y'all worry about that. Just wanted to weigh in.

Love you guys!

[MateoCerquetella]

Same for me!

[omerson-cruz]

Yes, this would be great feature too :)

[patroza]

There's a plan to make it work with application launched directly as node file_name.js.

how's that going @ArtemGovorov ? we could really use this atm.

[suryarajendhran]

Adding a comment here so the team knows that there's a lot of demand for this feature!

[tarwich]

Apologies for the necro, but I tried using this a little last week, and couldn't get it to work.

❯ console-ninja node test.js
fish: Unknown command: console-ninja

bash-3.2$ console-ninja node test.js
bash: console-ninja: command not found

I've tried

• Running as a task
• Running as a shell command
• Running console-ninja
• Running /Users/.../.vscode/extensions/wallabyjs.console-ninja-0.0.91/out/shell/console-ninja
• Uninstalling and reinstalling
• Resetting all settings

Can't figure out how this is supposed to be working.

node: 14.21.2
Operating System:
  darwin: 22.3.0
  arch: x64

[patroza]

@tarwich
so the extension in vscode has installed console-ninja to my bin:
~/.local/bin/console-ninja

don't know if you need a more recent node.

[tarwich]

Thanks @patroza that's definitely what I suspected. I don't have that file.

❯ ls -la1 ~/.local
./
../
share/
state/

I've uninstalled, rebooted, installed the extension. Will continue to google. If you're comfortable sharing, what's the contents of your ~/.localbin/console-ninja file? I have this:

❯ cat ~/.vscode/extensions/wallabyjs.console-ninja-0.0.91/out/shell/console-ninja
#!/bin/sh
export NODE_OPTIONS='--no-warnings --loader "<REPLACE>"';
$@

❯ ls -l1 ~/.vscode/**/console-ninja
~/.vscode/extensions/wallabyjs.console-ninja-0.0.91/out/shell/console-ninja

[tarwich]

Found something useful in the log...

info host creating /Users/.../.console-ninja/.bin
info host installing /Users/.../.console-ninja/.bin/loader.js
info host installing /Users/.../.console-ninja/.bin/console-ninja
info host installing /usr/local/bin/console-ninja
ERR! host failed to create symbolic link EACCES: permission denied, symlink '/Users/.../.console-ninja/.bin/console-ninja' -> '/usr/local/bin/console-ninja'

Continuing looking for data...

❯ ls -la1 ~/.console-ninja/.bin
./
../
console-ninja*
loader.js

Experiment 1 (fail)

Trying this:

 ~/.console-ninja/.bin/console-ninja npm run dev

didn't work.

Let console ninja make the .local/bin stuff...

mkdir -p ~/.local/bin
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.profile

Restart vscode...

❯ ls -la1 ~/.local/bin
./
../
console-ninja@

Ok... better...

Experiment 2 (fail)

test.js

console.log('test');
new Promise(resolve => { setTimeout(resolve, 5000); })
.then(() => console.log('done'));

❯ console-ninja node test.js
test
done

Still not working, but progress was made

[tarwich]

Ok. Updated my node to @16 and it connected.

[NikGovorov]

Thanks for sharing the details, we'll change the installation process to include shell profile scripts change (prepending to PATH variables) and mention the min version of nodejs in our docs.