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

[json] IntelliSense don't work for @angular in package.json #24321

Closed
albrin opened this issue Apr 8, 2017 · 7 comments
Closed

[json] IntelliSense don't work for @angular in package.json #24321

albrin opened this issue Apr 8, 2017 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality json JSON support issues verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@albrin
Copy link

albrin commented Apr 8, 2017

  • VSCode Version: 1.11.1
  • OS Version: Windows 10 Pro (License ;))

Steps to Reproduce:

  1. Open file "package.json" in Visual Studio Code
  2. Start typing "@ang" and press Ctrl+Space
  3. I get "No offers"
@aeschli aeschli added feature-request Request for new features or functionality json JSON support issues labels Apr 10, 2017
@aeschli aeschli added this to the Backlog milestone Apr 10, 2017
@aeschli
Copy link
Contributor

aeschli commented Apr 10, 2017

I have to investigate again, but NPM doesn't seem to provide a query API for scopes: npm/npm#8244

@XmlmXmlmX
Copy link

What about private package registries @aeschli. Are they not supported as well?

@XmlmXmlmX
Copy link

@aeschli I found the answer: #7430

No

@simeyla
Copy link

simeyla commented Jun 6, 2017

Why does every tiny thing I try to do with Angular result in a wild goose chase :-(

Anyway I'm assuming most people finding this issue just want to get intellisense to verify if the latest version is installed.

A workaround is the following command will which show the latest version of each installed package, and is much faster than attempting intellisense for each item anyway. Run it from the directory containing package.json.

PM> npm outdated
Package                      Current  Wanted       Latest  Location
@types/node                   6.0.77  6.0.77       7.0.27  rrcrm
typescript                     2.3.2   2.3.2        2.3.4  rrcrm

So I now know angular 4 (or 5 or 6 or whatever it is called now) is up to date :-)

@XmlmXmlmX
Copy link

Nothing new here? There is a similar request at developercommunity.visualstudio.com (concerning vs2017).

@aeschli aeschli changed the title IntelliSense don't work for @angular in package.json [json] IntelliSense don't work for @angular in package.json Nov 21, 2017
@aeschli aeschli modified the milestones: Backlog, November 2017 Nov 21, 2017
@aeschli
Copy link
Contributor

aeschli commented Nov 21, 2017

I added completions support for scoped types using https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md#get-v1search

Some limitations:

  • There seems to be no way to query all known, public scopes, so we have a hardcoded list (currently just @types and @angular). I'm happy to add more.
  • Completing in the packages should work for all public scopes
  • The API is filtering a lot of entries, so @types/m will not find 'mocha'. It will appear after typing more characters.

@aeschli aeschli added the verification-needed Verification of issue is requested label Dec 4, 2017
@dbaeumer
Copy link
Member

dbaeumer commented Dec 5, 2017

Verified that @types and @angular is working

@dbaeumer dbaeumer added the verified Verification succeeded label Dec 5, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality json JSON support issues verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants