What do you mean by not being seen? You try to require one of its namespaces in the repl and it cannot be found?

@U096GDTLL How exactly are you starting your REPL? Are you supplying both :dev:test aliases, or just :dev?

Correct, repl cannot use the dep. I am using :dev:test

@U096GDTLL I would verify that by starting a REPL outside VS Code, using the :dev:test alias combo, and making sure you can require/import those test-only dependencies.

If that works, then I double-check exactly how VS Code is starting a REPL.

(FWIW, I always start my REPL outside VS Code because it tends to run for days or weeks whereas I'm restarting VS Code a lot more often)

Cool, I will give it a shot

same result unfortunately

clojure -Sdeps '{:deps {nrepl/nrepl {:mvn/version,"0.9.0"},cider/cider-nrepl {:mvn/version,"0.27.4"}}}' -M:dev:test -m nrepl.cmdline --middleware "[cider.nrepl/cider-middleware]"

If you are using profiles, then you should also give +default (or the alias/profile you want to activate).

i currently don't have any profiles yet

any chance you could share what your test alias looks like? (anonymized perhaps?)

:test {:extra-paths ["components/the-component/test"
                               ]
                     :extra-deps {poly/the-component {:local/root "components/the-component"}}}
                               

pretty much it

I think I see it

Does poly/the-component reference this dep you seem to be missing in its :test alias?

yeah, that component has the dependency in its local deps.edn

under the extra deps in test of course

okay

you'll need to add that dependency of the-component as a test dep in the top deps.edn

you are referring to the-component there, but tools.deps will only pull in the-component's top-level (non-aliased) deps via such a reference

ah, so i have to do it more at a global level

I thought @U096GDTLL said this was already in "the test profile in the root deps.edn file" but re-reading it I think he just had the test path, not the extra dependency?

correct

i only defined the dependency in the components dep.edn

workspace/components/the-component/deps.edn

if you want to follow the poly convention, you'd do this in your top level deps.edn:

:dev {:extra-paths ["components/the-component/src"] ;; cursive workaround
       :extra-deps {poly/the-component {:local/root "components/the-component"}}}
:test {:extra-paths ["components/the-component/test"] ;; tools deps workaround
         :extra-deps {that-test-dependency-you-are-missing { ...coordinates...}}}

gotcha, ok. that does work. Misconception on my part

I suspect this would be less of a foot-gun if poly test constructed the dependencies for :dev:test the same way it does for projects? It reads all of the bricks' :test deps to build the classpath when running tests for projects I think? Or am I misremembering?

Hmm, no, looking at our projects deps.edn files, we have deps in :test that are duplicated from bricks' deps.edn :test aliases it seems...

(our setup is slightly complicated by the fact that we're in the process of migrating legacy stuff to Polylith, so our bricks are used by legacy subprojects for dev/test/build as well as from projects 😕 )

easy to get lost in the deps stuff sometimes for me, lol

@U04V70XH6 I think you remember right. The difference is that you rarely if ever dev-repl into a project that is not the development project

Excellent timing!

Feedback is welcome 🙂

I suppose I have to write some tests now :thinking_face: