Update @fimbul/valtyr to the latest version 🚀

[greenkeeper]

Version 0.8.0 of @fimbul/valtyr was just published.

Dependency	@fimbul/valtyr
Current Version	0.7.0
Type	devDependency

The version 0.8.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 @fimbul/valtyr.

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

v0.8.0

Features:

• new rule: no-invalid-assertion
• no-inferred-empty-object checks JSX elements and tagged templates starting from typescript@2.9.0
• no-useless-initializer checks destructuring defaults

Bugfixes:

• no-inferred-empty-object correctly checks classes with constructor
• no-inferred-empty-object correctly checks classes from JavaScript files that have type parameters in JSDoc
• no-useless-assertion forbids definite assignment assertions on properties with computed name
• no-return-await wraps object literals returned from shorthand arrow functions in parentheses to avoid syntax errors
• no-useless-spread no longer autofixes object spread to avoid introducing duplicate key errors
• --project flag no longer causes a crash when referencing non-existent files
• valtyr correctly loads custom formatters

Thanks to @aervin for contributing.

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 🌴