Raven is distributed in a few different methods, but they all should be included inside the <head> of your page.

You should try and include Raven as high up on the page as possible. Ideally, you’d like to include Raven first, in order to potentially catch errors from other JavaScript files.

Using our CDN

We serve our own builds off of Amazon CloudFront. They are accessible over both http and https, so we recommend leaving the protocol off.

<script src="//"></script>

If you’re feeling adventurous, we also host a master build, which should be considered potentially unstable, but bleeding edge.

<script src="//"></script> also gives us SPDY support! Again, just leave the protocol off, and it’ll do it’s magic.

<script src="//"></script>


We also provide a way to deploy Raven via bower. Useful if you want serve your scripts instead relying on CDNs and mantain a component.json with a list of dependencies and versions.

bower install raven-js

Please note that it automatically deploys the tracekit requirement and you should link it before raven-js.

<script src="/components/tracekit/tracekit.js"></script>
<script src="/components/raven-js/src/raven.js"></script>

Also note that both files are uncompresed but are ready to pass to any decent JavaScript compressor like uglify or closure.

Project Versions

Table Of Contents

Previous topic


Next topic


This Page