Ember auto type acquisition doesn't work

[robgraeber]

• VSCode Version: 1.34.0
• OS Version: OS X 10.14.2

I've been trying to get the @ember/* types to work automatically without installing @types/ember. The automatic type acquisition doesn't seem to work out of the box. I've tried creating a jsconfig.json file with all sorts of combinations in the typeAcquistion.include field. I saw someone post last year that it was working out of the box for them, so wanted to confirm it is still supported.

Steps to Reproduce:

Load the attached default ember project, and npm install.
Go to test-component.js and see if the types work for the @ember/* imports.

ember-example.zip
tsserver.log

Does this issue occur when all extensions are disabled?: Yes

[mjbvz]

Does this reproduce in the latest VS Code insiders build? Your example project worked for me without installing @types/ember and without creating a jsconfig.json:

From the logs it does look like automatic type acquisition is failing for you for some reason in VS Code1.34 though. Can you open the folder that contains the TS Server log file you share and look for a file called ti-xxx.log. This is the typings install log. It may have useful information about what is going wrong

[robgraeber]

Thanks for looking at it, I figured out the issue. The company I work for apparently needs to whitelist npm packages before they can be used so it was 404ing on types-registry.

For future searchers here was my ti-xxx.log:

[16:23:30.677] Updating types-registry npm package...
[16:23:30.677] Exec: "/usr/local/bin/npm" install --ignore-scripts types-registry@latest
[16:23:31.740]     Failed. stdout:
    
    stderr:
    npm ERR! code E404
    npm ERR! 404 Not Found: types-registry@latest

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/rgraeber/.npm/_logs/2019-06-03T23_23_31_724Z-debug.log

[robgraeber]

Hey @mjbvz did something change in VS Code v1.35.1? The ember type acquisition doesn't seem to work for me any more in the sample project above. The log says stuff like:
Package '@ember/component' is scoped and currently is not supported

ti-57347.log

[mjbvz]

Moving upstream. Someone on the TS team should know more about what the expected behavior is here

[sheetalkamat]

@RyanCavanaugh @DanielRosenwasser I thought silent failure (except logging in ti log) was expected behaviour. What do you think should happen here? send some kind of event or something to the editor?

[DanielRosenwasser]

Wait, is there still a reason that we can't do ATA for scoped packages?