Update codelyzer to the latest version 🚀

[greenkeeper]

Version 4.0.0 of codelyzer was just published.

Dependency	codelyzer
Current Version	3.2.2
Type	devDependency

The version 4.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of codelyzer.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

4.0.0

Features

• Support for Angular version 5 #409 0217e2d
• Rule for checking the name events without the prefix on https://angular.io/guide/styleguide#dont-prefix-output-properties #449 8f2b4e7.

Enable the new rule by adding the following line in your tslint.json config file:

"no-on-prefix-output-name": true

Thanks to @eromano for the rule implementation!

Breaking Changes

• The rules templates-use-public, no-access-missing-member, invoke-injectable and template-to-ng-template no longer exist. Remove them from your tslint.json configuration.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[greenkeeper]

Version 4.0.1 just got published.

Update to this version instead 🚀

Release Notes

4.0.1

Bug Fixes

• Fix noOutputOnPrefixRule and rename it to no-output-on-prefix. You can now enable it with:

"no-output-on-prefix": true

• Fix broken tests for noOutputOnPrefixRule.

[greenkeeper]

Version 4.0.2 just got published.

Update to this version instead 🚀

Release Notes

4.0.2

Bug Fixes

• Two issues in angular-whitespace related to check-semicolon and check-interpolation #469 2ef7438
• Check multiple semicolons inside the directive expressions #472 e6036d2

Thanks to @sagittarius-rev for the bug fixes!