bhauman/devcards-template

Template doesn't work

Opened this issue · 11 comments

When I create a new project with this template, and then type
"lein figwheel"
and then navigate to the home page, I see a blank page and when I pull up the browser's debugging tools, I see that there was an error trying to find the var start-devcard-ui!

Gotcha, I'll look into it this morning.

You have to wait for the project to compile. This can take a while for the first compilation of the project.

You should see a Successfully compiled message in the console when it's finished compiling. Then load or reload the project into the browser.

Does that work for you?

When I type lein figwheel, at the console I see the following messages:
Compiling ClojureScript.
Figwheel: Starting server at http://localhost:3449
Figwheel: Serving files from '(dev-resources|resources)/public'

At that point, I use Chrome to navigate to:
http://localhost:3449/devcards/index.html

In the browser console I get the error:
Uncaught TypeError: Cannot read property 'call' of undefined
and when I click on that error it takes me to line 12 of core.cljs, which is:
(dc/start-devcard-ui!)

When you type lein figwheel at the console you will see these messages:

Compiling ClojureScript.
Figwheel: Starting server at http://localhost:3449
Figwheel: Serving files from '(dev-resources|resources)/public'

At this point before you open the browser you need to wait until you see the following message:

Successfully compiled "resources/public/devcards/js/compiled/<your_project_name>_devcards.js" in 32.854 seconds.

After you see that message you should be able to load "localhost:3449/devcards/index.html" into the browser and it should work for you. This is something that needs to be done for the first compilation.

Does that work for you?

It never prints the message that it has successfully compiled, even after
running for hours.

On Thu, Aug 21, 2014 at 6:45 AM, Bruce Hauman notifications@github.com
wrote:

When you type lein figwheel at the console you will see these messages:

Compiling ClojureScript.
Figwheel: Starting server at http://localhost:3449
Figwheel: Serving files from '(dev-resources|resources)/public'

At this point before you open the browser you need to wait until you see
the following message:

Successfully compiled
"resources/public/devcards/js/compiled/hello_world_devcards.js" in 32.854
seconds.

After you see that message you should be able to load
"localhost:3449/devcards/index.html" into the browser and it should work
for you. This is something that needs to be done for the first compilation.

Does that work for you?

Reply to this email directly or view it on GitHub
#3 (comment)
.

What browser and OS are you using?

Windows 8. I've tried to pull the site up on both Firefox and Chrome; it's
not surprising it doesn't work on either given that it never prints that
message you mentioned that I should be seeing that it has successfully
compiled.

On Sat, Aug 23, 2014 at 4:20 PM, Bruce Hauman notifications@github.com
wrote:

What browser and OS are you using?

Reply to this email directly or view it on GitHub
#3 (comment)
.

Alrighty, I'm gonna have to get a VM running so I can check Windows out. Sorry for about this.

Actually let's try one more thing, Mark.

First do a lein cljsbuild clean
$ lein cljsbuild clean

And then do a

$ lein figwheel

Then what happens?

On Aug 24, 2014, at 1:59 AM, Mark Engelberg notifications@github.com wrote:

Windows 8. I've tried to pull the site up on both Firefox and Chrome; it's
not surprising it doesn't work on either given that it never prints that
message you mentioned that I should be seeing that it has successfully
compiled.

On Sat, Aug 23, 2014 at 4:20 PM, Bruce Hauman notifications@github.com
wrote:

What browser and OS are you using?

Reply to this email directly or view it on GitHub
#3 (comment)
.


Reply to this email directly or view it on GitHub.

More messages upon executing lein figwheel (see below), but ultimately the
result is the same -- when I visit http://localhost:3449/devcards/index.html
I still get the same error reported to the browser's developer console and
the page consequently doesn't render.

Compiling ClojureScript.
Figwheel: Starting server at http://localhost:3449
Figwheel: Serving files from '(dev-resources|resources)/public'
Compiling "resources/public/devcards/js/compiled/devcards_devcards.js" from
["de
vcards_src" "src"]...
WARNING: unsigned-bit-shift-right already refers to:
#'clojure.core/unsigned-bit
-shift-right in namespace: cljs.core, being replaced by:
#'cljs.core/unsigned-bi
t-shift-right
←[32mSuccessfully compiled
"resources/public/devcards/js/compiled/devcards_devca
rds.js" in 8.075 seconds.←[0m
notifying browser that file changed:
/devcards/js/compiled/devcards_devcards.js

notifying browser that file changed: /devcards/js/compiled/out/goog/deps.js
notifying browser that file changed:
/devcards/js/compiled/out/devcards/core.js

notifying browser that file changed:
/devcards/js/compiled/out/devcards_devcard
s/core.js

On Sun, Aug 24, 2014 at 2:14 PM, Bruce Hauman notifications@github.com
wrote:

Actually let's try one more thing, Mark.

First do a lein cljsbuild clean
$ lein cljsbuild clean

And then do a

$ lein figwheel

Then what happens?

On Aug 24, 2014, at 1:59 AM, Mark Engelberg notifications@github.com
wrote:

Windows 8. I've tried to pull the site up on both Firefox and Chrome;
it's
not surprising it doesn't work on either given that it never prints that
message you mentioned that I should be seeing that it has successfully
compiled.

On Sat, Aug 23, 2014 at 4:20 PM, Bruce Hauman notifications@github.com

wrote:

What browser and OS are you using?

Reply to this email directly or view it on GitHub
<
https://github.com/bhauman/devcards-template/issues/3#issuecomment-53170081>

.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#3 (comment)
.

Can this issue be closed? If not, can someone confirm that the more recent releases are still having problems on your machine? Note that if you are using version 0.2.1-7 from clojars the change from #20 still needs to be applied manually, but other than that it seems to work fine on Windows 10 at least.