Background

目前使用qiankun2.x的版本，业务提出需求在发布新的版本时候，期望可以不刷新页面（主应用暂时不考虑）进行该系统的热重载。类似于pc端的热更新，期望qiankun可以导出unload方法，完全销毁app的生命周期，业务系统再次将其重载。

Proposal

1. 翻看源码发现不能热更新的原因是因为import-html-entry中缓存了 embedHTMLCache
2. qiankun在importEntry时，如果已经获取过html资源，每次获取的都是内存中的html，以至于script & style也是缓存的
3. 我的解决方案是，在import-html-entry中导出根据app去清除缓存的钩子函数
4. 在qiankun中包裹其方法，根据single-spa的appStatus进行卸载应用

I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.

This because we now have the @opencomponents organization and quite few repos, and i

steps to do:

• add it here https://github.com/SAP/luigi/blob/546cf9f4a8e907ae4606a09f90dde06f649f125f/core/src/services/web-components.js#L36, like getCurrentLocale: window.Luigi.i18n().getCurrentLocale

🐞 Bug Report

Describe the bug

In this example code, the log parameter is defaulted to an empty object, but then line 28 references clonedLog.request.metaData which is not defined.

https://github.com/americanexpress/one-app/blob/7b9858c7283f3d9a4b742b7d63390615d11a789d/prod-sample/sample-modules/frank-lloyd-root/0.0.0/src/config.js#L24-L28

To Reproduce

If you write a test

Now when you create a new component using dcm init it'll generate a package.json file with your dependencies set to some static version we hard-coded. In the process of creating the component dcm can check on npm and see what is the latest version that makes sense and initialize the component with that (i.e. there should be some strategy other than taking the latest but not something too com