oracledb 5.1.0 → 5.4.0

package/package/README.md

@@ -16,8 +16,8 @@ In a clone or copy of the repository:
 
   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.
+  related build metadata information files from all `package/Staging`
+  directories to the `package/Staging` directory on one machine.
 
 - Run `npm run buildpackage`.  This calls `buildpackage.js` to make the
   node-oracledb package containing the node-oracledb JavaScript files, the
@@ -28,22 +28,22 @@ In a clone or copy of the repository:
 
 # Package Installation
 
-- As part of an `npm install` that uses the created package, the `package.json`
+- When running `npm install` with 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
+- If installation succeeds, space conscious users can then run `npm run prune`
+  which removes pre-built binaries for all other architectures.
+
+- If `npm install` fails because a suitable binary is not available, 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 architectures.
-
 The
-[`package.json`](https://github.com/oracle/node-oracledb/blob/master/package.json)
+[`package.json`](https://github.com/oracle/node-oracledb/blob/main/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

package/package/install.js

@@ -1,4 +1,4 @@
-/* Copyright (c) 2017, 2020, Oracle and/or its affiliates. All rights reserved. */
+/* Copyright (c) 2017, 2022, Oracle and/or its affiliates. */
 
 /******************************************************************************
  *
@@ -76,7 +76,7 @@ function done(err) {
     }
 
     log('********************************************************************************');
-    log('** Node-oracledb ' + nodbUtil.PACKAGE_JSON_VERSION + ' installed for Node.js ' + process.versions.node + ' (' + process.platform + ', ' + process.arch +')');
+    log('** Node-oracledb ' + nodbUtil.PACKAGE_JSON_VERSION + ' installed in Node.js ' + process.versions.node + ' (' + process.platform + ', ' + process.arch + ')');
     log('**');
     log('** To use node-oracledb:');
     log('** - Oracle Client libraries (' + arch + ') must be available.');
@@ -86,11 +86,12 @@ function done(err) {
   }
 }
 
-// Check for a usable binary file for the node-oracledb module.
-// Node.js 8.16 and 10.16 (and 12.0) contain an important N-API
-// performance regression fix.  If you're using the obsolete Node.js 9
-// or 11 versions, install will work but you're on your own regarding
-// performance and functionality.
+// Check for a usable binary file for the node-oracledb module.  Node.js 8.16
+// and 10.16 (and 12.0) contain an important Node-API performance regression fix.
+// Note that the checked versions are the minimum required for Node-API
+// compatibility; as new Node.js versions are released, older Node.js versions
+// are dropped from the node-oracledb test plan.  For example, the obsolete
+// Node.js 9 and 11 versions are not tested.
 
 function checkAvailable(cb) {
   let vs = process.version.substring(1).split(".").map(Number);

package/package/prunebinaries.js

@@ -1,4 +1,4 @@
-/* Copyright (c) 2019, Oracle and/or its affiliates. All rights reserved. */
+/* Copyright (c) 2019, 2022, Oracle and/or its affiliates. */
 
 /******************************************************************************
  *
@@ -19,13 +19,12 @@
  *   prunebinaries.js
  *
  * DESCRIPTION
- *   Removes pre-built binaries for all other Node.js releases and architectures.
- *   It keeps only the binary for the current Node.js version and architecture.
+ *   Removes pre-built binaries for all other architectures.
  *   This can be used to reduce the footprint of a node-oracledb install.
  *
  * USAGE
  *   Invoke this from the top level directory.
- *   After an 'npm install oracledb' installs pre-built binaries it
+ *   After an 'npm install oracledb' installs pre-built binaries, this file
  *   can be run with 'npm run prune'.
  *
  *****************************************************************************/
@@ -46,6 +45,6 @@ try {
       fs.unlinkSync(dir + '/' + f[i]);
     }
   }
-} catch(err) {
+} catch (err) {
   console.error(err.message);
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "oracledb",
-  "version": "5.1.0",
-  "description": "A Node.js module for Oracle Database access",
+  "version": "5.4.0",
+  "description": "A Node.js module for Oracle Database access from JavaScript and TypeScript",
   "license": "Apache-2.0",
   "homepage": "http://oracle.github.io/node-oracledb/",
   "keywords": [