This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Netbeans already lists all the NPM Libraries under the "npm Libraries" folder node in the project tree view. The problem is that you cannot do anything with the entries listed there. It would be very handy if the IDE would open the main entry file of each library that is defined in each library's respective package.json file.
Nice idea, we could perhaps add an action "Open main file". Thanks for reporting.
that would be great, but even double clicking the file at this point would be great, because you cannot even right click it o_O? On that note, there really should be a right click and I basically inherently expect to see the following: * uninstall module (if it is an npm module (other such modules include symlinks which are not directly controlled by NPM)) * update (won't work for symlinks) * upgrade (will bump the version) I also would love to see the IDE get really smart and allow us to add custom aliases which can resolve to custom module paths. This kind of relates to issue: https://netbeans.org/bugzilla/show_bug.cgi?id=262659 where I have a require() that points to a module that doesn't exist. If this sub-feature was added, it should appear here as a different Color. The biggest issue here that Netbeans just really needs to understand, is that because of the nature of javascript projects, we really REALLY need much more configurability with these projects at a module level. Almost every single developer I work with, tends to work with javascript slightly differently so things like this are a must have. Other things that can affect the type of module, and thus how the module is displayed in the libraries node include: .babelrc, package.json and variables inside the package.json such as the browserify fields which make the module a browserify plugin.