This course has been updated! We now recommend you take the AWS for Front-End Engineers (ft. S3, Cloudfront & Route 53) course.
Transcript from the "Exercise 2: Enhancing our Build Tools" Lesson
>> Kevin Whinnery: Now it's time for the next exercise portion of our morning. Where you fix more stuff in the example code project. So, to correspond with exercise number two. We've got some more GitHub issues for you to take a look at.
>> Kevin Whinnery: They are tagged with exercise two.
[00:01:17] If you if you want to take a crack at that task. So that is number one. For bonus points actually on this task, I didn't actually call it out here, but if you look in the EJS template which renders our TODO MVC page, there's a little bit of conditional logic in there that inserts a script tag to the minified version of app.css if we're in the production environment.
[00:02:03] The other one that I put out there was to add an NPM start script that is dedicated just for running migrations. I think you'll probably notice something in the package.json that already does run the migrations but post start, which is what it's currently assigned to, can do lots of other things.
[00:02:31] So it might be nice to have an NPM script which just runs migrations using the sequelize command line tool. And so, for that you'll have to learn a slightly different incantation to actually run that and make it work. So, adding a special purpose migration command to our NPM start NPM scripts will be another thing you could work on.
[00:02:55] And those are the two I got, but I'm getting like unsolicited pull requests for all kinds of stuff which is awesome. It's working, I'm very stoked at what you guys are doing with this.