![]() It would be nice to run something like yarn shadow-cljs -A:parent-alias -parent-deps "./" compile script or from a root directory run clj -A:shadow-cljs:deliverableB watch script. ![]() In order to allow everything to work together either poly must be aware of shadow-cljs or shadow-cljs needs to work more like clj. (perhaps if there is a root shadow-cljs.edn with all the project builds, but specifics are delegated down, this could work?)Ģ.2) shadow-cljs cannot reference aliases in a parent dir deps.ednģ) :local/root dependencies work with shadow delegating to deps but only for loading src not loading shared test code.Ĥ) deps.edn has deprecated referencing outside project directories "./xxx" and so polycan only work either by symlinks or a root deps.edn. The current constraints are:ġ) The poly tool is unaware of shadow-clj.edn so is unable to reason about dependencies unless information is duplicated.Ģ) shadow-cljs is unable to be run from a parent directory like clj is able to and it hard codes the location of shadow-cljs.ednĢ.1) -config-merge doesn't work delegating to a lower directory as it can only merge into a known build and you cannot add a build. This does mean that the the poly tool is unaware of the project dependencies unless I duplicate them in an unused project deps.edn. So the way I'm using shadow-cljs with polylith is to not use projects/deliverableA/deps.edn to define dependencies and instead use (example proj) to define dependencies and source paths. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |