Carsten Leue

Thanks, that already helps a step further. Looks like this has to include the transitive dependencies, too. The new code is: ```typescript globals: { // The key here is library...

@tinesoft I have succeeded in building a bundle without boostrap, but using a different approach than the quickstart lib. I am now using https://www.npmjs.com/package/ng-packagr to create the bundle, specifying ng-bootstrap...

https://github.com/ng-bootstrap/ng-bootstrap/issues/2107

@alan-agius4 independent of the discussion how `npm link` works, is there any usecase for including `devDependencies` in a package published to npm? If not, I would second the request to...

Hi @nohajc looks like the PR is not merged because of https://github.com/google/martian/pull/344#issuecomment-1195738697 Would you be able to comply to these requirements?

Hi @franchb I am not familiar with neither the fx package nor the jetstream package. From what I understand your code is doing the following: - it makes use of...

Suggestion https://github.com/containers/podman/issues/22682#issuecomment-2216754294 is working for me, too, but I was hoping for a podman only solution @rhatdan

I have a generic component that dynamically instantiates another component based on configuration returned via a REST request. The generic component is loaded at bootstrap time, the dynamic component is...

Because that turns out to be the wrong one, that instance does not find the dynamically loaded components. The constructor of PageComponent actually looks like this: ```typescript constructor(aFctResolver: ComponentFactoryResolver, aActivatedRoute:...

**Answer to the second question, first:** The different components are not supposed to be addressed via different routes. It is a business requirement that the routes need to stay stable,...