fix: ignore unknown logger properties#4
Closed
Fixes #2. Skips creating a `new Proxy` if `prop` isn't a known property of `logger`. This seems to work: * `Object.hasOwn(console, "log")` -> `true` * `Object.hasOwn(console, "other")` -> `false` Before this change, running `require("not-a-log").default.other` would crash with the error in #2. Now it returns `undefined`.
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by JoshuaKGoldberg and has received 0 comments.
Add a comment
Comment form would go here