Skip to content
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

Problem with multiple source paths #41

Closed
lgrapenthin opened this issue Jan 20, 2015 · 7 comments
Closed

Problem with multiple source paths #41

lgrapenthin opened this issue Jan 20, 2015 · 7 comments

Comments

@lgrapenthin
Copy link

I am not sure if this is a problem with piggieback or weasel and would need some time to narrow it down if this is necessary:

I have a cljs.user namespace in my /src/dev/cljs/cljs/user.cljs. "src/dev/cljs" is part of the cljsbuild source vector if I am in the dev profile.

I also have a myproject.core namespace in /src/cljs/myproject/core.cljs. "src/cljs/" is obviosuly also part of the cljsbuild source vector.

When I start the weasel REPL, it complains that it can't find myproject.core. This is happening with weasel 0.5.0, clojurescript 2665 and cljsbuild-0.1.5-SNAPSHOT. With Clojurescript 2511, piggieback 0.1.3 and weasel 0.4.2 I don't have the problem.

@mfikes
Copy link
Contributor

mfikes commented Jan 20, 2015

Perhaps this is a duplicate of #28

@lgrapenthin
Copy link
Author

Seems very likely. But the error directly refers to the ns form instead of specific vars.

@mfikes
Copy link
Contributor

mfikes commented Jan 20, 2015

@lgrapenthin Right. Currently you get ExceptionInfo No such namespace errors with the latest ClojureScript releases, but previously the same root cause would result in WARNING: Referred var xxx.yyy/zzz does not exist warnings.

I created a reduction in the form of a minimal repository capable of reproducing it: https://github.com/mfikes/weasel-src-paths

@lgrapenthin
Copy link
Author

Unless this is slurped somewhere, I currently don't get the WARNING (versions specified above).

@jaen
Copy link

jaen commented Feb 10, 2015

Also hit me when #44 fixed another issue I was having.
The :source-paths workaround doesn't seem to work for me though.

EDIT: scratch that, the workaround works, I just can't stop doing typos to save my life

@the-kenny
Copy link
Contributor

For the record: In order to be able to require your own project's CLJS-Namespaces, you have to add the source-directories to leiningens :source-paths.

@tomjakubowski
Copy link
Collaborator

Closing as a duplicate of #28. Feel free to ping this issue if a subsequent fix for #28 doesn't fix your issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants