Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Jonathan GrieveTreehouse Moderator 90,705 Points
A bit of fun with React Router :)
I'm really enjoying the relatively recent React Router 4 course and I've finished the first section.
Until now, I've been running the project directly on my localhost development server just as I did with the React Basics course because there I had an instant connection to the app. Then it occurred to me since we were using Create React App to make the project, I didn't need to as we had Webpack Dev Server to host it on.
So I copied the project over to my regular project folder to keep all my stuff in one location.
Then something funny happened. The server still compiles correctly with a number of warning messages. Like this:
There are multiple modules with names that only differ in casing. This can lead to unexpected behavior when compiling on a filesystem with other case-semantic. Use equal casing. Compare these module identifiers: * F:\path\to\node_modules\object-assign\index.js Used by 1 module(s), i. e.
I've had a look but don't really see a fix that more fits my situation. But is it worth trying to fix this considering I still have a successful compilation? Thanks :)