-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Warning when running Figwheel without cleaning #511
Comments
This is really a clojurescript analysis caching thing. Somehow you are
getting an clojurescript anaylsis cache that is stale and doesn't include
your symbol. But this is not a figwheel problem per se.
A couple of things can happen to where your javascript runtime env and your
anaylsis cache get out of sync.
One thing to remember is to do a hard shift reload even if your browser
devtools have caching disabled. The sucker caches anyway.
If you save the said file its symbols will get into the analysis and this
will go away.
…On Wed, Jan 11, 2017 at 7:17 PM, Radon Rosborough ***@***.***> wrote:
See reagent-project/reagent-template#132 (comment)
<reagent-project/reagent-template#132 (comment)>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#511 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAKQHmdttW8rJ3oVI_sgCKtiFocn2Xnks5rRXE1gaJpZM4LhMwQ>
.
|
It seems like this is definitely a bug somewhere, though. Should I attempt to reproduce the issue without Figwheel? I'm not sure how to do that. |
I understand that it's strange and can be disconcerting but I would ask that you get some more experience before tracking this down. It may in fact be a bug but there is a bunch of knowledge you need to understand so that you actively help us determine what's going on.
For example reproduce the behavior with a lein new figwheel test-repl project.
But if you are new to clojurescript I would let this go for now and just know that this is entirely normal and not necessarily a bug and it is very dependent on how you set up your project.
…Sent from my iPhone
On Jan 11, 2017, at 8:49 PM, Radon Rosborough ***@***.***> wrote:
It seems like this is definitely a bug somewhere, though. Should I attempt to reproduce the issue without Figwheel? I'm not sure how to do that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In short, if I run
lein figwheel
twice, without cleaning in between, then in the second session I get a compiler warning any time I try to access a variable—even though the variable is defined, and its value is correctly printed.Here are the precise steps to reproduce, along with my version and OS information:
Additional info:
lein clean
before runninglein figwheel
the second time.~/.m2
repository before performing the same steps as above.localhost:3449
before starting Figwheel or after.localhost:3449
or0.0.0.0:3449
.The text was updated successfully, but these errors were encountered: