-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support tools.deps #56
Comments
thanks for reporting this and sorry for delay. Could you elaborate more and give some examples how such integration would look like? You need rules to emit deps.edn? Or you need a rule that consumes deps.edn? |
Hello, and thanks for replying. Since you asked: I have a multiproject monorepo which provides two clojurescript front ends and a dozen backend artifatcts. Historically we followed the pattern described here and have moved to the third way of organizing our code described therein. This means we use no tools other than the
n.b.: To build a backend artifact:
n.b.: My ideal bazel rules would look similar to the
Following this . It also means that the same rules can support clojurescript once you have your node dependencies installed via AFAIK, using Lastly, to hash-lock external dependencies, it would be great if we could add
Adding that extra key doesn't break anything but I asked alex miller and he wasn't sure whether the extra key would be passed along internally, but there is a way in I'm happy to answer any questions or help if I can. |
@jasonh-logic2020 thanks for clarification. I'll try to take a look as soon as I can. Or if you willing to contribute I'm absolutely open to it. |
Hello and thanks for making this. I would not be able to use clojure at work without it.
Is there any chance of supporting tools.deps, by which I mean using the clojure cli to report dependencies, classpaths, and names (library and binary) from deps.edn?
The text was updated successfully, but these errors were encountered: