You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a project recently, where I had to support IE11. I ran into a problem, where the modules compiled by bit were not transpiled properly, therefore ended up using the entry source file from the package folder, and transpiled it as a dependency.
I am using vue-cli and what I did was
Changed the import from
import VuexWizard from '@bit/cleverclip.cleverclip-vue-components.navigation.vuex-wizard/dist/navigation/vuex-wizard.umd'
To
import VuexWizard from '@bit/cleverclip.cleverclip-vue-components.navigation.vuex-wizard/VuexWizard/index.js'
And added the following in my vue.config.js
transpileDependencies: [
/@bit/
],
I wonder, if there's a better way to do it, preferably to have the module created by bit transpiled by default.
this is already available for bit v15 for react components.
with vue support you will be able to set compilation targets as yo urequire for vue as well.
update vue support is gonna be its own epic, so i'm closing this ticket
#2254 # Description
I had a project recently, where I had to support IE11. I ran into a problem, where the modules compiled by bit were not transpiled properly, therefore ended up using the entry source file from the package folder, and transpiled it as a dependency.
I am using vue-cli and what I did was
Changed the import from
To
And added the following in my vue.config.js
I wonder, if there's a better way to do it, preferably to have the module created by bit transpiled by default.
Specifications
The text was updated successfully, but these errors were encountered: