Draft: Partial deprecation of Cljsjs about packages

[Folcon]

I'd like to pipe up and say that at least from my perspective the below statement is not always true =)...

• To allow easy use of JS libraries from Cljs -> No longer needed

From my perspective the process of adding even one npm lib to a project can be incredibly hit and miss and I try to set aside at least a few days to ensure that it's working. Thankfully once it's running then it's usually possible to just leave it be.

Contrast that with any clojure/script lib which is basically copy deps, read the docs to work out how to use it...

This may be a minority opinion, but I don't believe that requiring all cljs devs to also maintain a detailed understanding in every javascript tool that's the new way to make things run in order to use npm libs is a great thing?

cljsjs at the very least provides a fairly consistent level of approachability to npm libraries. Sure they may be a tad out of date, but that can be tackled.

With regards to my build process, I'm using figwheel / webpack. So perhaps things are much better on the shadow-cljs side of things?

[yesudeep]

cljsjs works wonderfully with Bazel by default. I'm not sure this would be a good idea. npm can be unreliable. things break randomly.

Here's an example using Bazel: https://github.com/yesudeep/rules_clojure/blob/clojurescript-support/examples/setup/default/BUILD.bazel#L28

[Deraen]

Deprecation notice has been added to the readme: aa849fb