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

JavaScript Express Basics (2015) Using Templates with Express Scaffolding Your Project’s Templates - adding “partials”

Why teamtreehouse don't update their videos when a tool has been renamed or it version is no longer supported.

jade became pug, and node-inspector is no longer supported by the up-to-date version of node. but treehouse still using a 3 years old track! time to update !!!!!!!

Christopher Lebbano
Christopher Lebbano
15,338 Points

Does this mean I have to worry about anything I learn on this website to be outdated information?

6 Answers

Spencer Snyder
Spencer Snyder
4,030 Points

Hey guys, one thing I noticed is that tree house hasn't added many new js vids to the js track this year but has actually released a ton. Use the library and filter for JavaScript and sort by date for the latest and greatest vids. It's way better that way, and treehouse is on the cutting edge from what I've seen idk why they don't update their track to reflect that.

Spencer

5 months since the OP posted this and STILL nothing has been updated. Wow...

Like I said, in programming things change very rapidly. But to be honest, most of treehouse courses are up to date just some of its contents is outdated and needs to be updated. hopefully by raising concerns about this issue, treehouse may start paying attention to these minor outdated info.

I agree with Spencer! but I still think that treehouse needs to update their tracks on a regular basis. and that can be done by just having a troubleshooting team. if We take the problem that I had with Jade which it's now Pug, or even node-inspector that's no longer supported by the new versions of node, You can clearly see that other students raised the same concerns 4 to 6 month ago but still no updates were released.

Oualid Jniyah & Spencer Snyder:

Hope you are submitting comments under "Rate this Video" when the video ends like I have. The instructor who created the Express.js module lessons is no longer working at Treehouse. He didn't include links in the Teacher's Notes of his updated code in the index.jade & post.jade file in the previous lesson. Look under the previous lesson "Questions" underneath the video to find the index.jade code on the Community page. Jade.js had a trademark issue which is why the developer of the app had to change the name of the app to pug.js.

I'm trying to figure out how to adjust the entire Express.js module using Windows 10 OS Control Panel (not Mac 0S X) with git. I'm having issues with it as I'm very new to git & I haven't quite figured out how to use my Control Panel with it. (That's a subject of which I posted early in the Express.js module on the Community page.)

Oualid Jniyah, Christopher Lebbano, Spencer Snyder, & Edin Jusupovic:

I agree with all of you that JavaScript modules on the Full Stack JavaScript track have become outdated since they were filmed. I don't know how they schedule or when they schedule filming videos for updating modules to replace outdated modules. As you all know, this does take considerable time to do, & JavaScript libraries are updated over time. It's just the nature of the business.

The Jade.js/pug.js issue was a trademark issue that Treehouse wasn't aware of. That occurred after the video was filmed. (It's in the pug.js documentation.)

What I did, since I didn't have my own computer at the time, I just took written notes as best I could. I'm sure there will be a time when we will be able to figure out how to use the JavaScript libraries mentioned in the Full Stack JavaScript track since they've been updated. If we find problem issues with them, there is a way to contact the developers who created the libraries directly to inform them of bugs in their specific libraries. Treehouse isn't responsible for updating other developers' JavaScript libraries.

If any of you received a notice at the beginning of your Full Stack JavaScript track months ago telling you they were updating the track, you had the option of viewing the updates & accepting them or not. Whether you chose to update your track or not, the "Express Basics" module wasn't one of the modules that was removed & replaced with an updated module. It was just moved to a different location in the sequence of modules in the track.

Here's what I found out later in the Full Stack JavaScript track which I sent to the instructor. It's in regard to saving an EXACT version of a development dependency:

It's posted here: npm Basics > Installing Packages with npm > Managing Dependencies in the package.json File.

"It might have helped if you had mentioned "npm --save-exact," & "npm --save -E" with "npm --save" or "npm --save-dev --save-exact" flags to save the exact "bcrypt 0.8.3" version since "bcrypt 0.8.7" was the current version which appeared when doing this lesson at the time I did it. However, it might not have helped if the Workspaces "Python 2.7.5" was updated to "Python 3.5.0" since I did this lesson."

This concept was mentioned in the "Building a MEAN Application > Introduction to the MEAN Stack > Setting up an Express Application," Section 1, Video 3, lesson 4.

I don't know if this will help you or not. I didn't try it myself since I discovered this near the end of the track.