javascript - Node.jsnpm - anyway to tell if a package is pure JS or not? - Stack Overflow

admin管理员组

文章数量:1221411

I've noticed that in trying to get seemingly simple node packages to install with npm (e.g. nerve, a "micro-framework") I often run into some form of dependency pain. After some digging, I tracked down the problem with nerve to the bcrypt module, which is apparently written in C/C++ and has to be compiled after the package manager downloads it.

Unfortunately, it seems like if you want this to work on Windows, the answer is (from one of the bcrypt issues threads) "install a Linux VM". So earlier today I did just that, and started running into other dependencies (you need certain unnamed apt packages installed before you can even think about building, despite GCC being installed), then eventually after seeing yet another C compiler error (about some package or other not being able to find "Arrays.c" I think), I actually gave up, and switched from nerve to express instead. Ironically, the larger and more complicated express installs with npm on Linux and Windows without a single issue.

So, my question is: is there any filter / dependency tracking available that lets you see if a package has additional dependencies besides node core? Because to me the allure of node is "everything in Javascript", and this kind of stuff dispels the illusion quite unpleasantly. In fact, despite having done more than my time working with C/C++, whenever I see a requirement to "make" something these days I generally run in the other direction screaming. :)

I've noticed that in trying to get seemingly simple node packages to install with npm (e.g. nerve, a "micro-framework") I often run into some form of dependency pain. After some digging, I tracked down the problem with nerve to the bcrypt module, which is apparently written in C/C++ and has to be compiled after the package manager downloads it.

Unfortunately, it seems like if you want this to work on Windows, the answer is (from one of the bcrypt issues threads) "install a Linux VM". So earlier today I did just that, and started running into other dependencies (you need certain unnamed apt packages installed before you can even think about building, despite GCC being installed), then eventually after seeing yet another C compiler error (about some package or other not being able to find "Arrays.c" I think), I actually gave up, and switched from nerve to express instead. Ironically, the larger and more complicated express installs with npm on Linux and Windows without a single issue.

So, my question is: is there any filter / dependency tracking available that lets you see if a package has additional dependencies besides node core? Because to me the allure of node is "everything in Javascript", and this kind of stuff dispels the illusion quite unpleasantly. In fact, despite having done more than my time working with C/C++, whenever I see a requirement to "make" something these days I generally run in the other direction screaming. :)

• javascript
• node.js
• dependencies
• npm

Share Improve this question Follow edited May 23, 2017 at 10:31 CommunityBot 111 silver badge asked May 10, 2012 at 16:28 DaveDave 55611 gold badge77 silver badges1717 bronze badges 1

• 1 I feel your pain Dave, but some times we're forced down to c/c++ by optimization and resource demands. After working on a few native node modules and trying not to repeat anything and use reasonable dependencies, I've run into a number of issues. Perhaps the most rational node modules are those that call or execute native code as opposed to compile and link with it. – Mark Essel Commented Jun 13, 2012 at 20:35

Add a comment  | 

3 Answers 3

Sorted by: Reset to default 15

The first solution doesn't tell you if a dependency makes the package impure or not. Much better to search for gyp generated output:

find node_modules/ | grep binding.gyp || echo pure

Look out for the "scripts" field in the package.json.

If it contains something like

 "scripts": {
    "install": "make build",
 }

and a Makefile in the root directory, there's a good possibility that the package has some native module which would have to be compiled and built. Many packages include a Makefile only to compile tests.

This check on the package documents does not exclude the possibility that some dependency will have to be compiled and built. That would mean repeating this process for each dependency in the package.json, their dependencies and so on.

That said many modules have been updated to install, without build on Windows, express for one. However that cannot be assured of all packages.

Using a Linux VM seems to be the best alternative. Developing Node.js applications on Window gives you step by step instructions on installing a VM, Node.js and Express.

Node is not "everything javascript" , since one way to extend node core is to write c/c++ plugins.

So Node is more a javascript wrapper around c/c++ modules using V8.

How could you write efficient database drivers in pure javascript for instance ? it would be possible but slow.

as for the filters , it is up to the author to document his package. there is no automatic filter.

本文标签： javascriptNodejsnpmanyway to tell if a package is pure JS or notStack Overflow