Fix: Type Errors

[mosesintech]

This PR will fix certain type errors in @nextwp/core:

• add optional chaining to objects in getAllItems. (fixes errors 2 and 3 of Type Errors in Build #75)
• add Items type to allData array in getItems. (fixes error 4 of Type Errors in Build #75)
• add optional chaining to menu object in getMenuItems. (fixes errors 5 and 6 of Type Errors in Build #75)
• add any type to err in getOptionsPage catch block. (fixes error 8 of Type Errors in Build #75)
• add String() function and optional chaining to objects in getNodeInfo. (fixes error 10 of Type Errors in Build #75)
• add any type to err in getTaxonomies catch block. (fixes error 11 of Type Errors in Build #75)
• add optional chaining to getTaxonomyPage endpoint variable. (fixes error 12 of Type Errors in Build #75)
• add types to functions in get-archive-static-params.ts. (fixes errors 14 and 19 of Type Errors in Build #75)
• add Number()/String() functions and optional chaining to get-archive-static-params.ts functions. (fixes errors 15, 16, 17, and 18 of Type Errors in Build #75)
• add Number() and optional chaining to get-taxonomy-static-params.ts. (fixes errors 20, 21, and 22 of Type Errors in Build #75)
• add any type to err in revalidate catch block. (fixes error 23 of Type Errors in Build #75)

This does not fix the following errors of #75: 1, 7, 9, 13, 24, 25, or 26.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-wordpress-starter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 22, 2024 4:54pm
nextwp-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 22, 2024 4:54pm