{"_id":"@garfish/bridge-vue-v3","_rev":"138-4f7bcd08df1e291cc4309581c836ac7c","name":"@garfish/bridge-vue-v3","dist-tags":{"beta":"1.19.7-beta-20250911075322.0","latest":"1.19.12"},"versions":{"1.6.0-beta-20220526030938.0":{"name":"@garfish/bridge-vue-v3","version":"1.6.0-beta-20220526030938.0","keywords":["garfish","micro frontend","vueBridge"],"author":"danpeen content;\n}\n\nexport const provider = vueBridge({\n rootComponent: App,\n appOptions: ({ basename, dom, appName, props }) => {\n // pass the options to createApp. check hhttps://vuejs.org/api/application.html#createApp\n return {\n el: '#app',\n render: () => h(App),\n };\n },\n handleInstance: (vueInstance, { basename, dom, appName, props }) => {\n // you can do something in handleInstance after get the vueInstance\n vueInstance.use(newRouter(basename));\n vueInstance.provide(stateSymbol, createState());\n },\n});\n\n```\n\n## Contributing\n\n- [Contributing Guide](https://github.com/modern-js-dev/garfish/blob/main/CONTRIBUTING.md)\n\n## Credit\n\n- [single-spa](https://github.com/single-spa/single-spa) for community raised a hot wave of micro front-end solutions, and we refer to the implementation of the bridge part in [single-spa](https://github.com/single-spa/single-spa) and we think it is a good design, so we fork the code of the bridge implementation part and make some adjustments for the lifecycles in Garfish.\n","readmeFilename":""}