You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vars across :local/rootdeps.edn dependencies cannot be resolved, but their namespaces can (i.e. I can control-b the namespace and appear in the right one). Also I have deps with no names.
However refactoring the deps.edn to look like this works:
The problem seems to be that when deps are pulled in through :default-deps, deps doesn’t normalise the paths to absolute paths. Using the first (broken) example:
Reported by @favila in Slack:
When importing a project that looks somewhat like this (redacted):
Vars across
:local/root
deps.edn
dependencies cannot be resolved, but their namespaces can (i.e. I can control-b the namespace and appear in the right one). Also I have deps with no names.However refactoring the
deps.edn
to look like this works:The problem seems to be that when deps are pulled in through
:default-deps
, deps doesn’t normalise the paths to absolute paths. Using the first (broken) example:Using the second (working) example:
Here, the two libs come in via
:extra-deps
and top-level:deps
, and they are both absolute.The text was updated successfully, but these errors were encountered: