oracledb - npm Package Compare versions

Comparing version 4.0.0 to 4.0.1

CHANGELOG.md

 # Change Log
 
+## node-oracledb v4.0.1 (19 Aug 2019)
+
+**This release is under development**
+
+- Fixed a regression causing a segfault when setting `oracledb.connectionClass`
+  and not creating a pool ([ODPI-C change](https://github.com/oracle/odpi/commit/f945355f3e58e7337dd798cba0404ab5755f0692)).
+
+- Fixed a regression when enumerable properties were added to
+  `Object.prototype`.
+  ([#1129](https://github.com/oracle/node-oracledb/issues/1129)).
+
+- Fixed a regression with missing `metaData` from `connection.getStatementInfo()`
+
+- Fixed crashes with spurious subscription (e.g. CQN) notifications, and when
+  unsubscribing an invalid subscription.
+
+- A more meaningful error is returned when calling `connection.subscribe()` with
+  SQL that is not a SELECT statement ([ODPI-C
+  change](https://github.com/oracle/odpi/commit/f95846bef6cf70e8114cbbb59ca04fbe2e7a3903))
+
+- Fixed passing DbObjects and JavaScript objects as the `payload` attribute for
+  AQ message enqueues when using an object queue.
+
+- Made the error message for AQ `queue.deqMany(0)` the same NJS-005 given when a
+  negative number is used.
+
+- Fixed a compilation warning seen on Windows.
+
+- Improve portability of buildbinary.js, a package creation script ([#1129](https://github.com/oracle/node-oracledb/issues/1129)).
+
 ## node-oracledb v4.0.0 (25 Jul 2019)
@@ -4,0 +34,0 @@

package.json

 {
   "name": "oracledb",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "A Node.js module for Oracle Database access",
@@ -5,0 +5,0 @@ "license": "Apache-2.0",

package/README.md

 # Overview
 
 This directory is used for building the [node-oracledb npm
-package](https://www.npmjs.com/package/oracledb).  The scripts can
-also be used to create custom packages for hosting on a local server.
+package](https://www.npmjs.com/package/oracledb).  The scripts can also be used
+to create a custom package for hosting on a local server.
 
@@ -13,34 +13,40 @@ Most users do not need to use anything in this directory.
 
-- `npm run buildbinary` calls `buildbinary.js` to create a
-  node-oracledb binary for the current operating system.
+- Run `npm run buildbinary`.  This calls `buildbinary.js` to create a
+  node-oracledb binary for the current operating system.  Depending how Node.js
+  was installed, you may need to run `npm install node-gyp -g` first.
 
-- `npm run buildpackage` calls `buildpackage.js` to make the
-  node-oracledb package containing the node-oracledb JavaScript files,
-  the available binaries, and a package.json that has an `install`
-  script and a `prune` script.  The package will be created in the top
-  level directory.
+  You can run `npm run buildbinary` on each operating system architecture that
+  you want to include in your package.  Copy the node-oracledb binaries and
+  related build metadata information files to the `package/Staging` directory on
+  one machine.
 
-  Before executing `npm run buildpackage`, all node-oracledb binaries
-  and related build metadata information files from all operating
-  systems should be placed in the `package/Staging` directory.
+- Run `npm run buildpackage`.  This calls `buildpackage.js` to make the
+  node-oracledb package containing the node-oracledb JavaScript files, the
+  available binaries, and a `package.json` that has `install` and `prune` script
+  targets.  The package will be created in the top level directory.  It can be
+  uploaded to npmjs.com, or to your own local server, and then used as a
+  dependency in your projects.
 
 # Package Installation
 
-- As part of an `npm install` that uses the created package, the
-  `package.json` install script runs `install.js` to check a binary
-  module for the current Node.js and operating system is available.
+- As part of an `npm install` that uses the created package, the `package.json`
+  install script runs `install.js` to check the availability of a binary module
+  for the current Node.js version and operating system architecture.
 
-  If a suitable binary is not available, installation will fail.
-  Users must then compile node-oracledb using source code from GitHub.
-  Alternatively a different version of node-oracledb, Node.js, or
-  different operating system may have a suitable pre-built binary
-  available.
+  If a suitable binary is not available, installation will fail.  Users must
+  then compile node-oracledb using source code from GitHub.  Alternatively a
+  different version of node-oracledb, Node.js, or different operating system may
+  have a suitable pre-built binary available.  See
+  https://github.com/oracle/node-oracledb/releases for information about Node.js
+  versions and pre-built node-oracledb binaries.
 
-- After install, space conscious users can run `npm run prune` which
-  removes pre-built binaries for all other operating systems.
+- After install, space conscious users can run `npm run prune` which removes
+  pre-built binaries for all other architectures.
 
-By default the top level `package.json` doesn't have an `install`
-script target.  This means that node-gyp will be invoked to compile
-node-oracledb.  This allows installation from [source
-code](https://oracle.github.io/node-oracledb/INSTALL.html#github) (via
-GitHub) when no suitable pre-built binary is available.
+The
+[`package.json`](https://github.com/oracle/node-oracledb/blob/master/package.json)
+in GitHub doesn't have an `install` script target by default.  This means that
+node-gyp will be invoked to compile node-oracledb.  This allows installation
+from GitHub [source
+code](https://oracle.github.io/node-oracledb/INSTALL.html#github) when no
+suitable pre-built binary is available.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

Found 3 instances in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1949137

increased by0.14%

Number of medium supply chain risk alerts

0

decreased by-100%

No dependency changes