Hi @phawrylak - circling back today on issues.
We have discussed this in the core team over the last week and we are not going to bring CamlJs into the pnp scope. This decision doesn't reflect anything about this particular library but is more thinking about long-term implications. Because we value your suggestion I wanted to outline our thinking in declining this request:
If there are clear gaps where no tools/libraries/samples exists, those are the areas where we can discuss adding a new package into the pnp scope or adding to an existing package.
Next steps
What I would suggest as a path forward is to reach out to @andrei-markeev and see if he is still interested in maintaining the library actively. If not, you could propose that you fork it and maintain a "copy" so that you can make the changes you need. We are happy to have you demo the library on a call and help drive knowledge.
Welcome your thoughts as well. Thanks!
I also don鈥檛 see a point bringing whole internet under pnp banner ;)