Trigger Node type acquisition on matching shebang

[Mlocik97]

Version: 1.61.0
Commit: ee8c7def80afc00dd6e593ef12f37756d8f504ea
Date: 2021-10-07T18:11:02.929Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.11.0-37-generic

Steps to Reproduce:

1. npm init -y
2. set "type": "module"
3. creating new index.js file
4. writting fs doesn't sugget to import fs, so it doesn't add import fs from 'fs' line.

[mackelito]

Same issue here...

Version: 1.61.2
Commit: 6cba118ac49a1b88332f312a8f67186f7f3c1643
Date: 2021-10-19T15:49:28.381Z (1 wk ago)
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0

[andrewbranch]

Duplicate of #46521. We don't assume you want to reference Node typings until you do it once in a project. You can either install @types/node or write your first import of a Node builtin by hand.

[Mlocik97]

Can't we automatically start intellisense for node, if env is set to node? I mean when files contain

#!/usr/bin/env node

? It already should tell, content of file contain node code, and activate intellisense for it?

[andrewbranch]

Yeah, that's a good suggestion.