After upgrading to latest version (2.3.3) I started getting this error when calling fixtures.unload():

UnhandledPromiseRejectionWarning: MongoError: ns not found

The problem gets fixed when downgrading to version 2.2.1

Hey guys,

Ran into a confusing error today. I was accidentally trying to insert a document with an invalid ObjectId (1 character too short) and the error message I received as output was:

[error] no docs returned from file: "LendingFiles.ts". verify that a docs array was exported. note: if using .js files, use "module.exports", instead of "exports".

Took me a long time to pin down that there was a particular fixture that was failing the whole thing because of my bad ObjectId

for example.json convert the created_at and updated_at fields to fields of type Date

[
  {
    "name": "Foo",
    "created_at": "2020-11-07T12:56:59.301Z",
    "updated_at": "2014-11-07T12:56:59.301Z"
  }
]

Can I have multiple files for the same collection? The documentation says that I need a file with the name of the collection like: users.js but I want to put them into separate files like:

users.registered.js
users.samples.js
users.expired.js

Hello guys! Thanks a lot for a great job!

I have a question about how can I load some fixtures to my database without removing existing entries from the collection. My use case is that I have a list of categories in my app with some categories defined at the start by myself (these I want to load from fixtures) but users of the app can also create more categories. So what I want to do is to only add entries defined in fixtures but not removing existing ones. I did manage to do it by removing unload() function from my file but then I'm getting an error as it tries to add entries that already exist (the key name in the collection has to be unique).

My file looks like this:

require('dotenv').config();
const Fixtures = require('node-mongodb-fixtures');
const fixtures = new Fixtures({
  dir: './fixtures',
});

fixtures
  .connect(process.env.DB_CONNECTION_URL)
  .then(() => fixtures.load())
  .catch(e => console.error(e))
  .then(() => fixtures.disconnect());

As you can see I'm catching these errors so it works but I'm wondering if there is a better solution for my use case?

Thanks!

Hi,

Is it possible to drop only the documents that are declared in the fixtures and keep the documents that are already present in the database (created by other means)

Thanks :-)

Is there a version of this library that doesn't enforce the option promiseLibrary?

Disconnect doesn't return the promise.
「this._client.close()」have to be returned.

If I don't export an array in my collection.js file, then I must be confronted with an error, instead I get this error:

(.../node-mongodb-fixtures/lib/index.js:171:66) ReferenceError: file is not defined

I took a look at the source code and looks like you are using a variable named file that is not defined in the function, so maybe use the collection name instead, or pass the file to it!

here is the part of code in lib/index.js:

function bulkImportDocuments(db, mute) {
  return collectionName => docs => {
    if (!Array.isArray(docs)) {
      // prettier-ignore
      throw new Error( '[error] no docs returned from file: "' + file + // <<------- HERE
          '". verify that a docs array was exported. note: if using .js files, use "module.exports", instead of "exports".'
      );
    }
...

I just wonder how to relate two fixtures? lets say i have two schemas (users and comments). A comment document stores user_id as a referecen to user document. how this can be acheived through this lib?

fixed by @westyside. Thanks!

Hi, first of all, I'm not familiar with node-mongodb-fixtures, that's why my question can be strange, but I try to add some tests to my REST API. I'm using jest and my API is based on node/express/MongoDB, also I'm using fakingoose to generate an entity from the db schema.
So, the node-mongodb-fixtures take a mock entity and insert it to the db collection and drop it after all tests are done, am I right understand its workflow?