Publish to `npm` for `browserify` support

[twolfson]

In order to support browserify, a JS compiler that resolves dependencies as if they were npm dependencies, we should publish raven-js to npm.

https://github.com/substack/node-browserify

The changes that we need to make this happen:

• Rename package.json to raven-browser or similar
• Remove private property from package.json
• Get approval from maintainers

If you are concerned about the task of adding 2 more tasks when you release (i.e. bumping package.json version and running npm publish), then you might want to consider using foundry:

https://github.com/twolfson/foundry

[bobbyrenwick]

👍

[christophercliff]

👍

FYI, there is a fork published to npm, but it's rather out of date: https://www.npmjs.org/package/raven-js

@mattrobenolt Any interest in losing the fork and making the main repo CommonJS compatible and publishing releases to npm?

[mattrobenolt]

@christophercliff I'm ok with doing that, I just need someone to hand hold this and support it since I don't use browserify.

[clayzermk1]

👍 for browserify support

[moretti]

Any update? Essentially you just have to merge the PR that @clayzermk1 submitted (#261), remove "private": true from package.json and update the npm package.

[mattrobenolt]

Just merged #261. I think there are a few other issues/PR's to address, then I'll cut a release and try to get this onto npm.

Anyone here willing to test when I publish? Or want to give me instructions to test on my own? I don't want to break the public package that others depend on.

[mattrobenolt]

This is going to be awkward now having a package called raven and one called raven-js both in npm. 😞

I need to figure out a way to combine these two or something into something that can be used in both places.

[moretti]

Yeah I agree, it's confusing, it would be nice to figure out a way to combine them! 😃
I can test the package once it's published, I think it should work fine, though.

[mattrobenolt]

@moretti Thanks. I'm going through my backlog of issues and pull requests today so I'll try and cut a new version this afternoon unless there's a major reason I can't.

[clayzermk1]

@mattrobenolt

I need to figure out a way to combine these two or something into something that can be used in both places.

CommonJS 😉. I think it all boils down to whether raven's dependencies would work browser-side (I don't think they do currently).

Anyone here willing to test when I publish? Or want to give me instructions to test on my own? I don't want to break the public package that others depend on.

I would be more than happy to give it a go! 😄 Testing is easy, npm install raven-js should pull it down, check the package.json that the version matches the code base (make sure you tag the release in git before doing an npm publish).

[moretti]

The simplest way for combining these projects would be to define two different entry points: one for node.js and another one for browsers. This can be done by editing the "main" and the "browser" field in package.json:
https://github.com/substack/node-browserify#browser-field

Have a look, for example, at superagent's package.json:
https://github.com/visionmedia/superagent/blob/master/package.json

[tommoor]

This would be lovely.

[twolfson]

For what it's worth, since the opening of this issue I now prefer to always separate raven from the rest of my JS. If there is anything that would cause the compiled JS to fail and block raven from getting set up, then that is bad. As a result, I usually put it in its own script tag and initialize it before the other JS.

<script src="raven-with-init.js"></script>
<script src="index.min.js"></script>