6.0.2

• Loosen jest-environment-enzyme react peerDependency to support testing other react versions. (@evocateur)

6.0.1

• Fix jest-environment-enzyme to actually work with different react adapter versions. (@evocateur)

6.0.0

🛑 Breaking

• jest-environment-enzyme now requires you to install your enzyme-adapter to your project root. (@blainekasten)
  • In 5.0.0 we wrongfully didn't require developers to do that hoping we could manage it internally.
  • This resulted in bloated dependencies, and peerDependency errors.
  • This fix requires a tiny bit more work from the user but is correct!

🍾 Improvements

• Improve jasmine-enzymes error messages to not be contradicting. (@blainekasten)

5.0.3

• Fix an internal flowtype issue. (@fernandopasik)

5.0.2

• Improve the scope of what files eslint-config-jest-enzyme affects. (@blainekasten)

5.0.1

• Remove unnecassary rAF polyfill. (@SimenB)
• Fix flow typing for toHaveProp. (@theneva)
• Remove unused dependency from jest-environment-enzyme. (@SimenB)

5.0.0

🛑 Breaking

• Removed toBePresent and toBeEmpty in favor of a new matcher toExist. (@blainekasten)

🚀 New Features

• New Package! jest-environment-enzyme (@blainekasten)
• New Package! eslint-config-jest-enzyme (@blainekasten)
• New Matcher toBeEmptyRender to assert when a component returns null or undefined. (@theneva)
• toHaveStyle, toHaveProp and toHaveState now all can accept an object as a list of key,values to match against. (@blainekasten)
• Using yarn workspaces locally now. (@blainekasten)

🍾 Improvements

• Improved error message when using an enzyme-matcher assertion with a non-enzyme argument. (@blainekasten)
• Improve the message output from toHaveClassName. (@theneva)
• toBeChecked previously failed on undefined or null values, but is now fixed. (@pascalduez)

4.2.0

• Handle an array of styles in the toHaveStyle assertion (@dennis-tra)

4.1.1

• Transfer ownership to FormidableLabs

4.1.0

• Internal CI fixes (@blainekasten)
• Minor: toMatchElement ignores props by default now. This should not break anyones existing tests. If it does, please report it.
  If you want to test an element without matching the props, pass { ignoreProps: false } as a second argument. (@finnigantime)