window.getPublicPath is not a function about coexisting-vue-microfrontends

[yangangzhang]

window.getPublicPath is not a function

子项目中是否有set-public-path.js，是否正确引入

[wangxueyou110]

set-public-path.js:1 Uncaught TypeError: window.getPublicPath is not a function
at Object../src/set-public-path.js (set-public-path.js:1)
at webpack_require (bootstrap:723)
at fn (bootstrap:100)
at Module../src/main.js (HelloWorld.vue?7a45:1)
at webpack_require (bootstrap:723)
at fn (bootstrap:100)
at Object.0 (Home.vue?3b23:1)
at webpack_require (bootstrap:723)
at bootstrap:790
at bootstrap:790

图片上传不了

[wangxueyou110]

直接项目下下来，按他步骤跑不起来

[yangangzhang]

直接项目下下来，按他步骤跑不起来

1. 截图直接可以拖拽到github上，自动上传
2. 项目下载之后依赖是否安装正确，最好使用cnpm（重要）
3. 对，就是先把项目下来，别接入自己的项目，跑不起来，报错是什么？

[wangxueyou110]

1.截图直接可以拖拽到github上，自动上传好像失效了，我这边传不上

[wangxueyou110]

项目我就是用cnpm装的，我没有接自己的项目就是他的项目跑不起来

[wangxueyou110]

你项目下载下来可以跑吗

[wangxueyou110]

现在图片可以上传了，之前可能网不好

[wangxueyou110]

发现问题了，是有个端口被占用了

[yangangzhang]

现在图片可以上传了，之前可能网不好

1. 刚才重新下载项目测试了一下，可以跑起来。
2. 建议你删除所有的node_modules然后重新安装，在跑起来
3. 这个项目问题还是不少的，可以研究，最好是使用淘宝qiankun技术方案

[yangangzhang]

发现问题了，是有个端口被占用了

做微前端的项目，注意端口，因为从开发到部署，端口太多了，而且必须要严格kill

[joeldenning]

Note that I have updated this project to use systemjs-webpack-interop. This removed the getPublicPath function.

See 1253942 for more information.

[wenwen1995]

@joeldenning , Hi,can you tell us why to use systemjs-webpack-interop and removed the getPublicPath function ? I cannot understand..The reason just is which can set the webpack public path "on the fly" to work with the dynamic url for the bundle in SystemJS' import map ? But it requires systemjs@>=6 and webpack@>=4.30.0...I think it's not a good way.

[joeldenning]

systemjs-webpack-interop has some features that getPublicPath did not, including ability to calculate a public path that is multiple directories above where the entry file is.

Using systemjs@6 is part of the core team's recommended setup, which is why it is encouraged in this repo.

Vue CLI uses webpack@>=4.30, so I don't see that as a problem.

You can read more about why we're doing this at all and the reasoning behind it at https://single-spa.js.org/docs/faq/#code-splits