Feature Request | Allow Multiple Raven Instances

[mariawix]

This PR creates a new bundle exposing both Raven constructor and singleton.

This functionality has been mentioned before.

Our web application is constructed as a composite of multiple sub-applications, which run in the same tab or worker. Each sub-application is developed and managed independently by a separate group. Each one of these groups wants to have its own DSN so that it can monitor its sub-application independently. Besides that the main application has its own Raven singleton.
Thus we need both Raven constructor and Raven singleton and we’d like to avoid fetching / bundling Raven twice. Unfortunately, the current API doesn’t allow this.

[zivl]

why not creating a new index.js file as follows:

var singleton = require('./singleton');
var RavenConstructor = require('./raven');

module.exports = singleton;
module.exports.RavenConstructor = RavenConstructor;

and then point main in package.json file to index.js
I don't see a reason to touch the way Raven is packed (i.e. no need for grunt file changes)

[kamilogorek]

@zivl it can be resolved simply by adding this line to the singleton.js file:

module.exports.Client = RavenConstructor;

We already do this in Node, so we may also do it here as well.

[zivl]

@kamilogorek sure!
My thought was to keep the singleton.js cleaner but if you can go with that so its cool.
(even smaller change :) )

[kamilogorek]

@mariawix @zivl #1272
Let me close this one :)

[mariawix]

@zivl @kamilogorek I didn't want to change API of Raven, for me both changes are good.

Thanks!

[kamilogorek]

Published as 3.24.0 :)