Peter Muessig

@HymanZHAN Rgd. `includeAssets`: the assets can be accessed directly as the middleware can directly access the assets of the node modules. Therefore this is not needed. So `/resources/mynpmpkg/css/my.css` is always...

@HymanZHAN let's use the #1049 to track the feature request for the `addToNamespace` option being considered in the middleware. As said, this might be a bigger change and will also...

@HymanZHAN - you can take a look into the [resolveModule](https://github.com/ui5-community/ui5-ecosystem-showcase/blob/main/packages/ui5-tooling-modules/lib/util.js#L688) function The logic is as follows: [resolveModulePath](https://github.com/ui5-community/ui5-ecosystem-showcase/blob/main/packages/ui5-tooling-modules/lib/util.js#L715) 1.) one of the properties "browser", "import", "require", "default" in package.json > exports...

@HymanZHAN as mentioned above, we use https://github.com/ui5-community/ui5-ecosystem-showcase/issues/1049 to track the feature request for the addToNamespace option and close the issue here fore the other question.

@thodd : this morning I discussed with @codeworrior to not patch the api.json and rather create a `api-mixin[-xxx].json` next to the api.json which can be collected by the jsdoc generation...

Closed in favor of #1171

Hi @jGluchConsalit , I'm not the expert in the authentication scenarios but what I could imagine is that the cookies are still in the middleware although removed from the browser....

@nicoschoenteich - maybe we can talk about this PR?

@marianfoo : you also need to update the package-lock.json otherwise the build fails

Fix is includes in version `7.7.1`