Add $setOnInsert modifier

.github/workflows/npm-publish.yml

@@ -0,0 +1,47 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: nedb
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+      - run: npm ci
+      - run: npm test
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.npm_token}}
+
+  publish-gpr:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://npm.pkg.github.com/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

README.md

@@ -440,6 +440,7 @@ db.count({}, function (err, count) {
 * `update` specifies how the documents should be modified. It is either a new document or a set of modifiers (you cannot use both together, it doesn't make sense!)
   * A new document will replace the matched docs
   * The modifiers create the fields they need to modify if they don't exist, and you can apply them to subdocs. Available field modifiers are `$set` to change a field's value, `$unset` to delete a field, `$inc` to increment a field's value and `$min`/`$max` to change field's value, only if provided value is less/greater than current value. To work on arrays, you have `$push`, `$pop`, `$addToSet`, `$pull`, and the special `$each` and `$slice`. See examples below for the syntax.
+  * `$setOnInsert` will set a field if a new object is being inserted.
 * `options` is an object with two possible parameters
   * `multi` (defaults to `false`) which allows the modification of several documents if set to true
   * `upsert` (defaults to `false`) if you want to insert a new document corresponding to the `update` rules if your `query` doesn't match anything. If your `update` is a simple object with no modifiers, it is the inserted document. In the other case, the `query` is stripped from all operator recursively, and the `update` is applied to it.

lib/indexes.js

@@ -1,4 +1,4 @@
-var BinarySearchTree = require('binary-search-tree').AVLTree
+var BinarySearchTree = require('@yetzt/binary-search-tree').AVLTree
   , model = require('./model')
   , _ = require('underscore')
   , util = require('util')

lib/model.js

@@ -262,6 +262,16 @@ lastStepModifierFunctions.$unset = function (obj, field, value) {
 };
 
 
+/**
+ * Set a field on a new object
+ */
+lastStepModifierFunctions.$setOnInsert = function (obj, field, value) {
+  if (!obj._id) {
+    obj[field] = value;
+  }
+};
+
+
 /**
  * Push an element to the end of an array field
  * Optional modifier $each instead of value to push several values

lib/persistence.js

@@ -72,7 +72,7 @@ Persistence.ensureDirectoryExists = function (dir, cb) {
   var callback = cb || function () {}
     ;
 
-  storage.mkdirp(dir, function (err) { return callback(err); });
+  storage.mkdirp(dir).then(function() { return callback(); }).catch(callback);
 };