New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

node-cmake

Package Overview
Dependencies
Maintainers
1
Versions
23
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

node-cmake - npm Package Compare versions

Comparing version 1.0.2 to 1.0.3

2

package.json
{
"name": "node-cmake",
"author": "Colin Taylor <cjntaylor@gmail.com>",
"version": "1.0.2",
"version": "1.0.3",
"description": "A CMake-based build system for node.js native modules",

@@ -6,0 +6,0 @@ "keywords": [

@@ -54,3 +54,3 @@ Node CMake

CMake has long been a counter-argument and
[competitor](https://chromium.googlesource.com/external/gyp/+/master/docs/GypVsCMake.md)
[competitor](https://gyp.gsrc.io/docs/GypVsCMake.md)
to gyp. While the arguments outlined there are well reasoned, there are many

@@ -140,3 +140,3 @@ arguments as to why CMake is good build system for cross platform builds:

first argument, that can be used identically to any other CMake `target`. In
the example above, the target will be called '\<NAME OF PROJECT\>'
the example above, the target will be called '\<NAME OF MODULE\>'

@@ -340,5 +340,7 @@ CMake has extensive documentation online, which can be

The NodeJS find_package command uses the VERSION and COMPONENTS arguments
to support build-defined versions and variants. Specify the version
immediately after `NodeJS` to hard-code a version requirement:
to support build-defined versions and variants.
Specify the version immediately after `NodeJS` to hard-code a version
requirement:
```CMake

@@ -345,0 +347,0 @@ find_package(NodeJS 0.12.7)

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc