Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Michael Stambulyan
3,220 PointsCant get to "http://localhost:3000/todo_lists" PLEASE HELP
running Windows 10
http://localhost:3000 loads fine but "http://localhost:3000/todo_lists" loads this error page.
ExecJS::ProgramError in TodoLists#index
Showing C:/projects/odot/app/views/layouts/application.html.erb where line #6 raised:
TypeError: Object doesn't support this property or method
(in C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/turbolinks-2.5.3/lib/assets/javascripts/turbolinks.js.coffee)
Extracted source (around line #6):
3 <head>
4 <title>Odot</title>
5 <%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track' => true %>
6 <%= javascript_include_tag 'application', 'data-turbolinks-track' => true %>
7 <%= csrf_meta_tags %>
8 </head>
9 <body>
Rails.root: C:/projects/odot
Iain Simmons
Treehouse Moderator 32,305 PointsHi Michael Stambulyan, I've added some code blocks around your code to make it easier to read. Otherwise you can't see the 'extracted source' if you just paste it directly into the question here on the forums because it will try and turn it into actual HTML.
Please refer to the Markdown Cheatsheet (below each question/answer/comment box) for instructions on how to format code or errors.
Unfortunately I don't know enough Ruby to help you with this error... sorry!
3 Answers
Kevin Korte
28,149 PointsTry this: http://mech.xyz/how-to-fix-ruby-on-rails-turbolinks-js-coffee-error-windows/
And welcome to trying to run Ruby on Windows. If you're like me, you'll bang your head against the wall so much you'll eventually give up.
When you finally spend more time troubleshooting Windows related errors than developing in Ruby, but you're not quite ready to do a Linux install or buy a Mac, you can join me on Cloud 9. I use the free account here and you can honestly get a lot of mileage from the free account.
Michael Stambulyan
3,220 PointsTHANK YOU SO MUCH it worked, luckily I have a mac maybe ill just work on that since ruby and windows dont get along all that well
Kevin Korte
28,149 PointsGood to hear! I'd recommend it. I have a Mac too at home, so it's not a big deal, but my work computer is Windows and they haven't bought into the idea of me on a Mac yet, so in the meantime I tend to develop Ruby on Cloud9 from the Windows computer, since I'm in a Linux environment on Cloud 9, and things just "work".
Now you can wear a shirt that says "I tried Ruby on Windows and survived". I'll bow to any man or woman that can get Ruby to work consistently one Windows.
Richard Cain
Courses Plus Student 9,029 PointsI am fairly new to Linux(LinuxMint 17.1) but I found I was able to get everything except vagrant up and running just fine. I do have win7 but despite using it for years I still found it way harder to do.
Caleb Schmidt
Front End Web Development Techdegree Graduate 18,686 PointsAnybody else have another solution? This one didn't work for me unfortunately. I'm very new to Ruby on Rails, so I have no idea where to even begin.
Kevin Korte
28,149 PointsSame error? Same OS?
Caleb Schmidt
Front End Web Development Techdegree Graduate 18,686 PointsSame error. Windows 7 64 bit. I've tried your solution above and it doesn't work. I've tried installing two different versions of Node.js and neither of those seem to run
Michael Stambulyan
3,220 PointsMichael Stambulyan
3,220 PointsALSO when I used "bin/rake db:migrate" i get this error message "bin is not a recognized as an internal or external command,"
SO i just ran "rake db:migrate" instead