ember-cli VS ember-cli-eslint

Ember pioneered the standardised usage of global cli tool. This is a perfect way to give new users a good onboarding experience as well as existing users power tools for daily usage.

If you haven't already, you can install the Ember CLI using the following command:

It has detailed documentation, an API reference, and a guide for their CLI tool to provide a better developer experience. It also has a Discord server to get help instantly.

When you have a built a single-page-application using Ember CLI you have two options for starting your app locally. You can either use the CLI's ember serve command directly or you can use the handy npm alias that is created for you after generating a new Ember app: npm run start

The code change to improve performance was small. When adding server middleware or testem middleware check the options passed to ember-cli and if they contain the path flag then don't run typechecking. A small ember-cli update was also required. ember-cli would pass all the CLI flags to the server middleware, but not to the testem middleware. Without the ember-cli update, ember-cli-typechecking would not of been able to perform the check when testem middleware was added. Interesting to note that for each PR I spent a lot more time figuring out how to effectively test the changes than implement them.

We wanted to avoid making too many unnecessary changes in this app until after our upgrade step was over, so we turned a whole bunch of rules off in our .eslintrc. It makes sense that we had to turn off these rules, since many of them were telling us about how to turn our app into an Octane-style app. They will be useful after we finish the dependencies upgrade! We can learn more about each rule by searching for the rule name in the ember-cli-eslint source code.