@nuxtjs/axios - adding interceptor about legacy-modules HOT 6 CLOSED

Just moved the interceptor to directly before the get request within asyncData and that doesn't work either strangely enough - also if I use axios directly - I don't think this can be an issue with this plugin after seeing that.

from legacy-modules.

Actually, this is an error in the plugin.

// Don't throw unhandled promises in SSR context
    return this.app._nuxt.error.call({$options: this.app}, {
      message: error.message,
      statusCode: error.statusCode
    })

Because in SSR the error isn't passed I can't catch it and do whatever I want. How can we get around this one?

from legacy-modules.

@silverbackdan In latest commit, I've entirely removed that auto error handling logic. Would be nice having your comments on it before next release :)

from legacy-modules.

@pi0 Ooo I quite like that :) I didn't know if there was a reason why the promise wasn't rejected on server-side before but it is nice still having the standardised status and message. It'd certainly work for my needs still!

from legacy-modules.

Thanks for your review. Actually i think the problem with handled promises should be fixed on Nuxt itself because both fetch and asyncData are being called before actual Vue rendering.

from legacy-modules.

That's much better, I'll update to the latest commit tomorrow morning. Thanks for taking the time on this module.

from legacy-modules.