feat(vue): export vueInit func

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.

[Rockergmail]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

support export vueInit

[Rockergmail]

As to why we need export vueInit.
We tried serveral hacks to use Sentry in micro frontend app (using qiankun.js). See the thread here.
The working way is using Sentry in main app, and using custom transport. With the filename of stacks, we know which subapp causing the error, and then mapping the subapp dsn to the newUrl. Finally we change the newUrl to the transport.
But this way we can not listen errors of vue's components unless we add the custom errorHandler in Vue option. That's what vueInit has done.
So we need export vueInit

[AbhiPrasad]

I think this is a very reasonable request! Could you also update the docs to add this info? https://docs.sentry.io/platforms/javascript/guides/vue/

[Rockergmail]

I can't found the repo of docs for @sentry/vue. So I just write here. @AbhiPrasad

Vue 2/3 - Multiple Apps Initial Indepentently

import{createApp}from"vue3";importVuefrom"vue2";import*asSentryfrom"@sentry/vue";constappOne=createApp({// ...});Sentry.init({app: appOne});// Vue2 initialization before loaded asynchronously as a subappsetTimout(()=>{constappTwo=newVue({// ...})Sentry.vueInit(Vue)},0)// Vue3 initialization before loaded asynchronously as a subappsetTimout(()=>{constappThree=createApp({// ...});Sentry.vueInit(appThree)},1000)

[AbhiPrasad]

Talked about this as a team and decided we aren't going to proceed with this change, since you can just call attachErrorHandler and createTracingMixins by yourself if you need it, vueInit is just sugar over those functions.

We want to control the public API exposed to users - because it helps make future changes much easier (less breaking changes needed).

Thank you for opening a PR! Hopefully you can just vendor what you need here.