Transitive dart dependencies about clojuredart

[momerath42]

I don't know about others, but only the local/root case matters to me (and it would definitely be nice to have soon); I'd be happy to work on this, if it's a good candidate for getting my feet wet.

[cgrand]

After more thoughts on the problem:

• having our own file (not deps.edn) simplifies packaging but we lose some integration, we think the trade-off is ok because it only impacts authors of cljd libraries using dart deps
• we use resolve-deps to get a map of libs to paths
• we scan all deps for pubspec.yaml
• we create dummy projects under .clojuredart that we add as local deps to pubspec
• we name the dummy projects after either a she or the project name or both

[dupuchba]

@momerath42 that's very nice but I think but we need it ASAP so we are going to do it. But we could need some help on review, testing, design & co

[momerath42]

a76c09a is working great, with a bunch of dart dependencies pulled in from my other (root/local) project, as well as use of several of its .cljd files. Thanks!

[cgrand]

In a76c09a we implemented a way to handle dart dependencies (transitively across deps.edn).

For lib users: it should just work, add the lib to deps.edn and the next cljd command (compile, flutter, clean) will retrieve dart deps if needed.

For lib authors:

• declare dart deps in pubspec.yaml as usual
• when packaging as a jar, copy pubspec.yaml on the classpath before building (or add it to the root of the jar)

[dupuchba]

[ ] TODO: document it