4.0.2

Bug Fixes

• Add contents of bundleCSS to vendor CSS bundle (5faa710), closes #272

Reverts

• fix: Initially lint files with npm start (f16bd3a)

---

See all changes since the last release.

4.0.1

Bug Fixes

• Move cosmiconfig to dev dependencies 🙈 (90f4b33)

4.0.0

Another major release. Here are the breaking changes in a glance:

• Dropped support for Node.js v6 (requiring >= 8.6)
• Need to move and rename Husky settings
• Possible new linting errors due to ESLint related updates

See detailed migration information below.

Bug Fixes

• Add missing dev dependency (f8b022a)
• Fix linting errors introduced by updating ESLint, plugins and configs (6af486a)
• Initially lint files with npm start (57d1374)
• Loading images via webpack (44eb628)
• Resolve error running tests on Node 6 (16b9114)
• Update webpack and webpack-cli to fix build errors (023afe7), closes #264

Features

• Auto format code using prettier as pre-commit hook (1557458)
• Enable to define baumeister config in package.json (#270) (217bdd2), closes #246
• Move tooling configs to package.json (ab6594c), closes #270
• Update ESLint, plugins and shared configs to their latest versions (bee2cba)
• Update husky to v1.x.x (63238ad)
• Update Jest to v24.x.x and Babel to v7.x.x (6e1122c)
• Update production dependencies (1384a3a)

BREAKING CHANGES

• feat: Auto format code using prettier as pre-commit hook

  This commit 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.

• feat: Update husky to v1.x.x

  You need to update the husky config which can be autmated by running ./node_modules/.bin/husky-upgrade. See https://github.com/typicode/husky#upgrading-from-014 for details.

• feat: Update ESLint, plugins and shared configs to their latest versions

  This 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.

3.1.0

Bug Fixes

• bring back object-rest-spread babel plugin for client code (4b0ca35)

Features

• Add interactive menu to list and run the most important scripts (37c36e9)

---

See all changes since the last release.

3.0.1

Bug Fixes

• Improve quality of source maps (e6d22dd)
• Make it possible to use nested handlebars pages (5e533ba)

---

See all changes since the last release.

3.0.0

🎉 Yeah, version 3 is finally here 🎉

Let’s recap the most important changes since the last 2.x.x release:

• build: Replace Gulp with Webpack (and npm scripts) (b91adea)
• bootstrap: Upgrade to Bootstrap 4 (e4680b5)
  • See Bootstrap v4 migration guide to read about the most notable as well as breaking changes.
• polyfills: Dynamically import and lazy load polyfills (00aa0de), Relates to #235
  • This keeps the vendor bundle in modern browser smaller because
    polyfills are only loaded when the used browser actually needs them.

Notable Changes since the last beta

Code Refactoring

• scripts: serve build via npm run build:serve (ce2cc70)

Features

• add PRODUCTION constant to ESLint config (bb0c954)
• improve the cacheability of the vendor bundle (735f2e6)
• reduce noise in terminal (especially in watch mode) (90a84bd)
• setup Babel plugin transform-imports (da517ed)
• setup tree shaking (90561f9)

BREAKING CHANGES

• scripts: Change the npm script name fpr serving the dist directory from npm run build:check to npm run build:serve

• The webpack runtime has moved into a separate file. Therefore you need to add a reference to that file into your HTML / Handlebars file(s) before the vendor bundle:

  <!-- webpack runtime JS -->
  @@runtime.js
  
  <!-- Vendor JS -->
  @@vendor.js
  
  <!-- Own JS -->
  @@app.js

  See https://developers.google.com/web/fundamentals/performance/webpack/use-long-term-caching#webpack_runtime_code for details about the why.

---

See all changes since the last prerelease.

Migration Guide

Below you’ll find the list of all breaking changes since the last 2.x.x release and what you have to adapt.

• build: Gulp and all the tasks are gone. But most of the npm scripts still do what they did before. Here are the main scripts needed for developing and building your project.

  Command	Description
  npm start	Builds for development, starts a webserver, watches files for changes, rebuilds incremental and reloads your browser.
  npm test	Lints your JavaScript files and runs unit test via the Jest CLI.
  npm run test:watch	Runs unit test with Jests watch option.
  npm run build	Builds for production to dist directory.
  npm run build:serve	Starts a static fileserver serving the dist directory.
  npm run build:analyze	Starts »Webpack Bundle Analyzer« to visualize size of Webpack output files

  See scripts section in package.json for all available scripts.

• build: The bundled polyfills moved to the vendor bundle, the webpack runtime has moved into a separate file. Plus the references to the bundles have changed. You have to update the references in your HTML / Handlebars file(s):

  <!-- Bundled vendor CSS files -->
  @@vendor.css
  
  <!-- Our compiled and merged Sass files -->
  @@app.css
  
  […]
  
  <!-- webpack runtime JS -->
  @@runtime.js
  
  <!-- Bundled vendor CSS files -->
  @@vendor.css
  
  <!-- Our compiled and merged Sass files -->
  @@app.css

• polyfills: Polyfills are now dynamically imported and lazy loaded to decrease the size of the vendor bundle for modern browsers. See README for details.

• eslint: We ’ve added eslint-plugin-unicorn and eslint-plugin-import which might introduce new linting errors. You might want to turn off rules in /.eslintrc.json in case you find them too opinionated.

• baumeister.json: The properties bundleCSS and includeStaticFiles in baumeister.json have moved to vendor.bundleCSS and vendor.includeStaticFiles. You have to adapt these changes in case you have added dependencies via these properties.

• bootstrap: We’ve updated to Bootstrap 4. See Bootstrap v4 migration guide to read about the most notable as well as breaking changes.

---

See all changes since the last release.

3.0.0-beta.1

This is the last beta before the final 3.0.0 release 🎉

We are now going to address a few enhancements which might get into the final 3.0.0 release. See #235 for details.

Notable changes

Bug Fixes

• Open Webpack dev server with --host flag (8ffcc18)
• Referencing fonts from within Sass files (cefe987), closes #236

Features

• Dynamically import and lazy load polyfills (00aa0de), Relates to #235

---

See all changes since the last release.

3.0.0-beta.0

This is the first beta of the 3.0.0 release 🎉

We have a few enhancements which might get into the final 3.0.0 release. See #235 for details.

Notable changes

Code Refactoring

• baumeister.json: Rename properties related to vendor files (7ac3de1)

Features

• remove Yarn lockfile 👋🏻 (0d4cd1b)
• eslint: Simplify setup and include two additional plugins (57219c3)
• build: Replace Gulp with Webpack (and npm scripts) (b91adea)
• bootstrap: Upgrade to Bootstrap 4 (e4680b5)

BREAKING CHANGES

• build: Gulp and all the tasks are gone. But most of the npm scripts still do what they did before. Here are the main scripts needed for developing and building your project.

  Command	Description
  npm start	Builds for development, starts a webserver, watches files for changes, rebuilds incremental and reloads your browser.
  npm test	Lints your JavaScript files and runs unit test via the Jest CLI.
  npm run test:watch	Runs unit test with Jests watch option.
  npm run build	Builds for production to dist directory.
  npm run build:check	Starts a static fileserver serving the dist directory.
  npm run build:analyze	Starts »Webpack Bundle Analyzer« to visualize size of Webpack output files

  See scripts section in package.json for all available scripts.

• build: The bundled polyfills moved to the vendor bundle and the references to the bundles in default.hbs has changed to:

  <!-- Bundled vendor CSS files -->
  @@vendor.css
  
  <!-- Our compiled and merged Sass files -->
  @@app.css
  
  […]
  
  <!-- Vendor JS -->
  @@vendor.js
  
  <!-- Own JS -->
  @@app.js

• eslint: This adds eslint-plugin-unicorn and the eslint-plugin-import which might introduce new linting errors. You might want to turn off rules in /.eslintrc.json in case you find them too opinionated.

• baumeister.json: The properties bundleCSS and includeStaticFiles in baumeister.json are moved to vendor.bundleCSS and vendor.includeStaticFiles. You have to adapt these changes in case you have added dependencies via these properties.

• bootstrap: See Bootstrap v4 migration guide to read about the most notable as well as breaking changes.

---

See all changes since the last release.

2.0.2

Bug Fixes

• adapt breaking changes of updated dev dependencies (9c2ff57)
• update dependencies (d60d3e1)
• copy additional directories in src/assets to build directories (376d729)

---

See all changes since the last release.

2.0.1

Bug Fixes

• dependencies: update dev dependencies (3ffdd2e)

---

See all changes since the last release.