Suppresses static JavaScript completions

[kopischke]

With the TypeScript extension active, Nova stops offering completion suggestions in JavaScript files. Note by this I mean the static completions that come with Nova out of the box, not clips (I am aware of #86, but that was strictly clips and has been closed, which suggests this is a different bug).

To reproduce

Steps to reproduce the behavior:

1. Deactivate all extensions.
2. Open a new JS document.
3. Type “A”.
4. Nova suggests “Array” (et al.) as completion.
5. Activate the TypeScript extension.
6. Type “r” after the ”A” from step 4.

Expected behavior

Nova suggests “Array” (et al.) as completion.

Actual behavior

Nova does not suggest completions.

Environment

• Nova version: 7.4 (310378)
• Extension version: 2.4.0
• TypeScript version: not in project
• Sidebar information: Status Running, TypeScript Version 4.3.5
• macOS version: 11.5.2
• NodeJS information:
  • node version: v16.8.0
  • npm version: 7.21.0
  • installation method: homebrew

Extension console output

“TypeScript” console shows “activated”. The “TypeScript Language Server” console complains about /user/local/Cellar/node/16.8.0/bin/npm not being found (homebrew’s npm is a symlink to /usr/local/lib/node_modules/npm/bin/npm-cli.js).

[kresdjan]

Same with for in both .ts and .js

nova-typescript disabled ↓

nova-typescript enabled ↓

[kresdjan]

What is the status? Can this be fixed?

[JimFrostig]

It seems to work for me, when I manually restart the tsserver (kill it by the terminal and restart it with the extension). Maybe that's related and can help you fix this ?

[kresdjan]

That is great. I still can't get Nova's snippets working. Seems like they can't coexist with the TypeScript extension completion.

[apexskier]

⚠️ Archived: Although it was fun to build my nova extensions, I haven't ended up using Nova regularly and can't devote the time to maintenance. Feel free to reach out if you want to fork and start maintaining an alternative.