Release 4.0.0 · micromata/generator-baumeister

baumeister: Add missing dev dependency (c0b89a9)
baumeister: Fix linting errors introduced by updating ESLint, plugins and configs (f38ea91)
baumeister: Initially lint files with npm start (19e2e83)
baumeister: Loading images via webpack (ff0b206)
baumeister: Resolve error running tests on Node 6 (68744fe)
baumeister: Update webpack and webpack-cli to fix build errors (c820435), closes #69
generator: Add templates directory to lint-staged export path (82f7f84)

baumeister: Auto format code using prettier as pre-commit hook (6ea3dbf)
baumeister: Enable to define baumeister config in package.json (fcfdc6c)
baumeister: Move tooling configs to package.json (68f31d8), closes #270
baumeister: Update ESLint, plugins and shared configs to their latest versions (3c6be02)
baumeister: Update husky to v1.x.x (4f35c94)
baumeister: Update Jest to v24.x.x and Babel to v7.x.x (7ac9da2)
baumeister: Update production dependencies (4a54e3c)

baumeister: Auto formatting introduces a new dev dependency which requires Node.JS >= 8.6

We are using prettier to format JavaScript, JSON and SCSS files automatically before you commit your files to Git via a pre-commit hook.

The prettier settings are defined in .prettierrc in the project root. In case prettier is to opinated for you or you don’t want Prettier to change your files without the chance to review the changes you just have to delete the pre-commit hook with in the package.json:
```
"husky": {
  "hooks": {
    "post-merge": "npm install",
    "pre-commit": "lint-staged"
  }
}
```
But we totally recommend you to give this workflow a chance, because it’s just one more thing you don’t have to care about.
baumeister: Since the update to Husky v1.x.x you need to update the husky config which can be automated by running ./node_modules/.bin/husky-upgrade. See https://github.com/typicode/husky#upgrading-from-014 for details.
baumeister: The updates of ESLint, plugins and shared configs to their latest versions might break your build since new versions have introduced new rules which might introduce linting errors in your code base.

Tip: Run npm run eslint:fix to see which errors are autofixable. And remember to turn off rules in eslintConfig in case you find them too opinionated.

See all changes since the last release.

Provide feedback