2.0.1

• Adds support for nested routes in config (fixes #24)

2.0.0

This release includes a few key changes to the package. If you're migrating from v1.x.x please check out the migration guide. I don't anticipate any more core changes to the API, but please let me know in the issues tab if there is a problem with this current implementation.

• Sensible defaults: You no longer need to explicitly pass breadcrumb strings or components in. For example:
  /one/two --> Home / One / Two (with no route config passed).
• API change: when mapping over breadcrumbs. Instead of returning an array of objects like [{ breadcrumb, path, /* ... */ }] to the component using the HOC. We now just return a flat array of breadcrumb components with props included. This makes the rendering step a bit easier to read / use.
• There is a new options object with an optional excludePaths param to easily opt-out of generating breadcrumbs for certain paths
• withBreadcrumbs is now a default export

1.2.0

• Adds location object to each breadcrumb for more flexibility #23 thanks @mrchief. This is a breaking change only if you happen to be using the (not recommended, but supported) getBreadcrumbs exported function instead of the HOC itself.

1.1.2

• Support extending react-router route config with a breadcrumbs prop. Fixes #18 by no longer requiring breadcrumb to be present in route objects if it is not needed for that specific path.

1.1.1

• Fixes issue #13 by removing .mjs extension

1.1.0

• Added support for es6 module .mjs export. Thanks @mhelmer
• Dev dependency upgrades & cleanup

1.0.7

• Bug: Fixes an issue where some breadcrumb components can return Uncaught TypeError: Cannot call a class as a function

1.0.5

• Bump version to fix npm publish compiled build issue

1.0.4

1.0.4

1.0.3

• Add support for home "/" route matching: #3