fix: fix unsafe property access

[ntnyq]

This PR fixes the issue occurs while accessing an unsafe property.

Issue reproduction:

https://github.com/ntnyq/eslint-plugin-ntnyq/actions/runs/15802108983/job/44541751654?pr=126

[Copilot]

Pull Request Overview

A concise fix to improve safety when accessing properties in getJSDocComment by using optional chaining.

• Changed unsafe property access of prevSibling.declaration.type to use optional chaining.
• Ensured consistency in safely accessing properties for TSDeclareFunction checks.

[brettz9]

Thanks! Can I ask though--do you happen to know what the triggering code was?

[brettz9]

Also, looks like I needed to bump package.json engines to >=20.11.0 and update CI. Done. Would you mind rebasing on my latest commit?

[brettz9]

Released as part of v0.52.0 ... I'll look to add to eslint-plugin-jsdoc now as well.

[ntnyq]

The error happens while linting this line of code

https://github.com/ntnyq/eslint-plugin-ntnyq/blob/775405a5a684ccaa2aa6c76b5ad13c7d6d30e715/tests/internal.ts#L10

prevSibling is type ExportNamedDeclaration and has no declaration property.

[brettz9]

Ah, thanks! So there is such a thing as a declaration without a declaration--go figure! :-)

eslint-plugin-jsdoc updated with v51.1.2.