Error: ENOENT: no such file or directory, rename 'path/file.js~' -> 'path/file.js' (while using nodemon)

[rafaelferreiraql]

Now, I don't know if it's nodemon or nedb's fault, but sometimes I have to restart nodemon a couple times because this error comes up... Not a huge deal, but still annoying. Please note that I'm also using the --ignore flag so the file.js~ automatic refresh doesn't infinitely loop with nodemon's own automatic refresh, idk if this has something to do with my issue.

[fpassa]

What's the file path expected when is compiled into an executable file. For instance, in macOS my project works fine when running it with npm start

But, after packaging it with electron-package and attempting to execute it, the error appears by stating that Uncaught Error: ENOENT: no such file or directory, open filename - datastore.js:77

Where is supposed to be located the db file after application is packaged? Have this been tested (the NeDB) on compiled apps? If so, what's the path to use?

[chenyuansgit]

i have the same problem, when the error is happen, the content of the data file is clear, how to deal it？

[zearg]

up, i have the same problem when electron app is in an ASAR package

[zergius-eggstream]

I met the same problem, but i found that error appears when creating multiple instances of datastore with same filename. You have to instantialize datastore only once and keep reference across whole app. May be developers should provide singleton/factory (for example var db = require('nedb').open({filename: 'path/to/file'}) ) instead of creating instances

[heyuncoder]

when i use var db = require('nedb').open({filename: 'path/to/file'}) ) ,
i get an error: require(...).open is not a function

[gabrielmicko]

I have the same issue in tests... .open is not defined. I can't find any workaround so far.

[JamesMGreene]

We don’t need a new API to have singletons, just abstract it with a local module of your own, e.g.

db.js:

const Datastore = require('nedb');

const db = {
  tableName: new Datastore({ filename: '...' })
};
module.exports = db;

[thrazu]

Check if you are trying to open two or more connections at once. In my case I'm opening two connections and get the error.

[xeroxstar]

Check if you are trying to open two or more connections at once. In my case I'm opening two connections and get the error.

How can we open two or more connections at once? I have this code that give me same error:

let collections = {
    users   : __dirname + '/db/bundles/users',
    scripts : __dirname + '/db/bundles/scripts'
};

for(let i in collections){
        collections[i] = new nedb({
            filename : collections[i],
            autoload : true
        })
}

[thrazu]

@xeroxstar your code tries to open multiple databases (files). What if you have just one file, let's say db.json and multiple 'tables': users, scripts etc. Try something like this:

import Datastore from 'nedb';
...
const db = new Datastore({ filename: '/db.json', autoload: true });

db.insert({ table: 'users', ...userdata }, (err) => {
    ...
})
db.insert({ table: 'scripts', ...scriptdata }, (err) => {
    ...
})

...
let collections = {
  users: [],
  scripts: []
};

db.find({ table: 'users' }, function (err, users) {
    // get all users
    // If no document is found, users is equal to []
   collections.users = users
});

This code wasn't tested.

[xeroxstar]

@xeroxstar your code tries to open multiple databases (files). What if you have just one file, let's say db.json and multiple 'tables': users, scripts etc. Try something like this:

import Datastore from 'nedb';
...
const db = new Datastore({ filename: '/db.json', autoload: true });

db.insert({ table: 'users', ...userdata }, (err) => {
    ...
})
db.insert({ table: 'scripts', ...scriptdata }, (err) => {
    ...
})

...
let collections = {
  users: [],
  scripts: []
};

db.find({ table: 'users' }, function (err, users) {
    // get all users
    // If no document is found, users is equal to []
   collections.users = users
});

This code wasn't tested.

thank for reply, yes you right, i guess i will do it if there is no solution to solve what i am trying to achieve...

[siarhei-klimuts]

I am using next.js api routes, and in development mode there a lot of HMR reloads, so extracting db to a module does not help, nothing helps so far.