Works like a charm. The smart tags are really nice although hard to reach in my eyes. I also like the watermarks very much because getting around in all those json files sometimes gets confusing. The description tooltips to the packages are very helpful. The package search needs some work maybe because sometimes totally wrong hits come up for autocompletion, not having to do with anything I typed.
Works as expected. The most unexpected benefit was the explanation of NPM's semver matching syntax (e.g ~ and ^). Really nice to see at a glance which is which. NuGet could benefit from something like this, hint hint :)
This is a great tool. I installed it yesterday, but I'm not able to get intellisense working (everything else is perfect).
A peek with fiddler reveals a DNS lookup failure for typeadhead.npmjs.com. Cannot hit it with a browser either. registry.npmjs.org calls are fine.
Temporary issue perhaps?
the search on bower or npm does not work.
Only a little search box is displayed (but know intellisense from the repository is displayed).
Does your extension have problems with other extensions like Resharper, DevExpress, WebEssentials?
Same here. All works perfectly but live search.
- I've installed nodejs, npm and bower.
- Set npm in path environment variable (C:\Users\user\AppData\Roaming\npm)
- Check my VS2013 version. (VS2013 + update 3)
- Configure My Firewall for Visual Studio 2013
I also try :
- Install nodejs tools for VS
- Set the path environment variable for git
i have no extension like webEssential, Resharper, or other ...
Maybe another path environment variable is necessary ? (for bower, gulp or other ?)
any idea ?
first of all, thanks for this nice extension! :)
However, whenever I install a package I have to navigate to the directory where the packages reside using the file system browser and drag & drop them into Visual Studio, because otherwise they won't show up in VS/the project. Since we are using TFS as SCM, they are also not checked in (until I do the described manual step). Is this simply a missing feature or am I failing somewhere?
you need to use something like grunt to copy the files to the correct place for referencing i.e. /Scripts. Take a look at the following article which describes the basic process.
I just installed the extension in Visual Studio 2013 (Update 4). I can see all the watermarks and package information in package.json, but I can't see the package information in bower.json. Why is that?
Thanks for very useful extension!
But I mostly use this extension on my job, through the corporate proxy.
So, extension does not work properly.
It would be nice if you implement proxy settings in this ext.
The tsd npm package (https://www.npmjs.com/package/tsd) is a common way of getting Typescript definition files stored in the borisyankov/DefinitelyTyped github repo. It relies on a tsd.json file similar to this one:
I know this file format is different fom the grunt.json and bower.json, and there're no package definitions built around these files also, but is there any possibility to have the Package Intellisense plugin extended to support "package" search, intellisense, install / uninstall for the tsd.json file?
Hmmm, this will be a rather large item to implement. I'm not sure it's easily done. But at least we can provide Intellisense for the structure of tsd.js using SchemaStore.org and Web Essentials, but to get package Intellisense will be much harder.