Fix check of node type

[Benjaminsson]

Closes #137

Seems that enzyme-adapter-react-16 was the one that broke the type checks. So this also bumps those versions to make sure the tests passes both before and after the bump.

[VincentLanglet]

Hi @Benjaminsson, thanks for your PR.
Can you add a test for the case you fix ?

[codecov]

Codecov Report

Merging #145 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #145   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           6      6           
  Lines         107    107           
  Branches       41     41           
=====================================
  Hits          107    107

Impacted Files	Coverage Δ
src/utils.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24d2c11...a79dc3d. Read the comment docs.

[codecov]

Codecov Report

Merging #145 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #145   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           6      6           
  Lines         107    107           
  Branches       41     41           
=====================================
  Hits          107    107

Impacted Files	Coverage Δ
src/utils.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24d2c11...a79dc3d. Read the comment docs.

[Benjaminsson]

@VincentLanglet I added a test case. I don't know how much value it gives. As you can see the test coverage was already 100% and it did actually break when updating the adapter. But might be a bit more future proof now? I'm not super experienced in testing but this should do the job right?

[VincentLanglet]

@Benjaminsson It's a good way for me to be sure the PR does the job.
And it avoid futur regressions.

Thanks !

[mycolaos]

Relating to the original issue #137, I'm wondering what will be printed in the snapshot? React.memo in place of Component? Shouldn't it be Memo(ComponentDisplayName)?