How to exit callback loop in javascript

Question

I have a simple codesnippet in a file test.js:

  [1, 2, 3, 4].forEach(function(e) {
        console.log(e);
    });

whenever I run node test.js in terminal I get the output

But the program never really exits. I am required to end it manually. It seems quite trivial but I am unable to figure out a proper way to exit the scrip in the terminal.

UPDATE 1:

var mongoose = require('mongoose');

var User = require('../models/users/user');
var UserProfile = require('../models/users/profile');

var config = require('../config');
var logger = require('../libraries/logger');
logger = logger.createLogger(config);

var connectionString = config.database.adapter + '://' + config.database.host + ':' + config.database.port + '/' + config.database.name;
mongoose.connect(connectionString, {server: {auto_reconnect: true }});

User.find(function(error, users) {
    users.forEach(function(user) {
    var data = {
        email: user.local.email || user.google.email || user.facebook.email || ''
    };
    UserProfile.update({user_id: user._id}, {$set: data}, function (error, record) {
        if (error) {
            logger.error(error);
        } else {
            logger.info(data);
        }
    });
});

Above is the code I am actually trying to make work. Adding process.exit() exits the process even without processing the script. Any solutions?

UPDATE 2:

I figured out the solution. In above case script wasn't exiting because connection to mongodb database wasn't closed.

I used a dirty hack to close the connection after processing is done by adding setTimeout(function() { mongoose.connection.close(); }, 60 * 1000); at the end of the line

it won't happen when it is a blocking script. But for non-blocking it seems to happen. I found how to make it work. But I don't understand why it is happening without using process.exit() — pntripathi9417
– pntripathi9417, Commented Nov 27, 2015 at 7:13
There is nothing non-blocking in the script you've posted? Please show us your actual code. Yes, non-blocking code can lead to node not terminating when written oddly. — Bergi
– Bergi, Commented Nov 27, 2015 at 7:21
I am under the impression that whenever we are using callbacks it is a non-blocking code. In the current example this is the case isn't it? — pntripathi9417
– pntripathi9417, Commented Nov 27, 2015 at 7:26

Binvention · Accepted Answer · 2015-11-28 04:37:03Z

1

If this is a nodejs question which it appears to be then you exit using process.exit() so you add that to the end of whatever function should run last. In your case you would close mongoose first and hen have the process.exit() as the success handler for the exiting of mongoose

edited Nov 28, 2015 at 4:37

answered Nov 26, 2015 at 17:01

Binvention

1,0771 gold badge9 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

pntripathi9417 Over a year ago

yes it is a nodejs script. I added process.exit() in the end of the file and it works. I wonder why it happened. Would you be able to explain what happened at the run time?

Binvention Over a year ago

Nodejs often times runs processes in the background so if your script doesn't have a specific end point it just keeps running

Binvention Over a year ago

And if it is the right answer please mark it as such.

Collectives™ on Stack Overflow

How to exit callback loop in javascript

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related