Ivar Conradi Østhus

I am in favor of supporting json logs. But I am not fully convinced we want to commit ourself to use log4js in the future. In fact, if you do...

Yes, I carefully copied of the `node-xmlint` npm package and included that as a package to the new package ([github source code](https://github.com/ivarconr/samlify-validator-js)). This was needed because the source code for...

> I have created @authenio/samlify-xmllint-wasm as the validator using xmllint-wasm. This is definitely the way to go. Removing hard dependencies on Java is a good thing for this project. CPU...

I looked in to you code. My biggest concern is the dependency on `xmllint-wasm` which heavily utilized worker threads on Node.js. I would rather not have that introduced in to...

To support AMD is pretty straight forward as you only have to deliver javascript-files in a well defined folder-structure. The real challenge is to find a way to define and...

Another complexity is to support dependencies to external modules. Should we require the user to provide this our should wro4j be able to retrieve it?

I will try to answer your questions in short: - _Do you agree with requirement to have a model used to analyze dependencies from? Or are there other alternatives?_ -...

To me this issue is divided in two parts: 1. **Deliver optimized AMD-resources** - No layering, no analyzis of dependencies etc. - regular pre/post processors - this is the easy...

**Could you define what do you understand by layer? It is important to have a common understanding of basic concepts.** A "layer" is basically a set of related script bundled...

After thinking a bit about the build-profile a lot of what it defines is redundant for wor4j, as a lot of the information is unnecessary. But some details are needed...