RavenJS triggers deprecations from jQuery Migrate

jQuery team provides a tool called jQuery Migrate to ease migration from version to version. It’s especially a nice tool when migrating from jQuery 1/2 to jQuery 3.

However, when using jQuery migrate and RavenJS, deprecations are triggered by this code https://github.com/getsentry/raven-js/blob/master/src/raven.js#L927-L934

        var $ = _window.jQuery || _window.$;
        if ($ && $.fn && $.fn.ready) {
            fill($.fn, 'ready', function (orig) {
                return function (fn) {
                    return orig.call(this, self.wrap(fn));
                };
            }, wrappedBuiltIns);
        }

[benvinegar]

@romainneutron – I think we’ll just remove this code, it serves less and less purpose today.

[tacman]

Thanks, Ben. That makes sense, we’ll check it out.

On Mon, Feb 6, 2017 at 3:57 PM, Ben Vinegar [e-mail] wrote:

@tacman https://github.com/tacman – for breadcrumbs Raven.js overrides console.log which causes log statements to appear to come from Raven.js. It definitely does not use jQuery.unique, so I suspect the deprecation notice is being triggered by somewhere in your own code / other library.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/getsentry/raven-js/issues/817#issuecomment-277810826, or mute the thread https://github.com/notifications/unsubscribe-auth/AAl0QbqJkZ0WeJNhuAcj3Z8Wnk2gfsoxks5rZ4kkgaJpZM4LcyP2 .