Feature-request: support "strict" mode when, instead of returning undefined, it throws with a descriptive error message

[dko-slapdash]

Feature-request.

Like if I do oc({abc: {zz: 10}}).abc.def.xyz(), instead of returning undefined, the library might throw an Error with description:

Cannot find abc.def.xyz path in the object, because abc.def doesn't exist.
Object: {abc: {zz: 10}}

The error message might be verbose enough to simplify debugging and pointing, which exact part didn't match.