Improve situation: Stormpath Application not ready about express-stormpath HOT 8 CLOSED

+1 on this. My supertest tests fail because my server starts up and requests are sent before the stormpath.init is complete.

from express-stormpath.

@robertjd and I have a solution for this which we will be working on in the near future. Right now we're working on cutting a new release with some new config options / etc., so once the dust has settled with that we'll be fixing bugs.

from express-stormpath.

+1

from express-stormpath.

Working on this now. Will update the issue as I make progress.

from express-stormpath.

You can now do this via the Express application object!

Here's how it works:

var app = express();

app.use(stormpath.init(...));

app.on('stormpath.ready', function() {
  console.log('Stormpath is ready to go!');
  app.listen(3000);
});

Doing things this way ensures your web server ONLY starts after Stormpath is 100% initialized.

from express-stormpath.

Currently updating the docs to show this in the examples =) This will ensure users don't run into this anymore.

from express-stormpath.

Also throwing in some unit tests to assert this behavior.

from express-stormpath.

Closing this via #88

from express-stormpath.