objcjs-types 0.4.0 → 0.5.0

package/dist/FileProvider/index.d.ts

@@ -94,6 +94,7 @@ export { NSFileProviderCreateItemOptions } from "./NSFileProviderCreateItemOptio
 export { NSFileProviderDeleteItemOptions } from "./NSFileProviderDeleteItemOptions.js";
 export { NSFileProviderDomainRemovalMode } from "./NSFileProviderDomainRemovalMode.js";
 export { NSFileProviderDomainTestingModes } from "./NSFileProviderDomainTestingModes.js";
+export { NSFileProviderErrorCode } from "./NSFileProviderErrorCode.js";
 export { NSFileProviderFetchContentsOptions } from "./NSFileProviderFetchContentsOptions.js";
 export { NSFileProviderFileSystemFlags } from "./NSFileProviderFileSystemFlags.js";
 export { NSFileProviderItemCapabilities } from "./NSFileProviderItemCapabilities.js";

package/dist/FileProvider/index.js

@@ -16,6 +16,7 @@ export { NSFileProviderCreateItemOptions } from "./NSFileProviderCreateItemOptio
 export { NSFileProviderDeleteItemOptions } from "./NSFileProviderDeleteItemOptions.js";
 export { NSFileProviderDomainRemovalMode } from "./NSFileProviderDomainRemovalMode.js";
 export { NSFileProviderDomainTestingModes } from "./NSFileProviderDomainTestingModes.js";
+export { NSFileProviderErrorCode } from "./NSFileProviderErrorCode.js";
 export { NSFileProviderFetchContentsOptions } from "./NSFileProviderFetchContentsOptions.js";
 export { NSFileProviderFileSystemFlags } from "./NSFileProviderFileSystemFlags.js";
 export { NSFileProviderItemCapabilities } from "./NSFileProviderItemCapabilities.js";

package/dist/FinderSync/FIFinderSync.d.ts

@@ -1,5 +1,7 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
+import type { _NSDictionary } from "../Foundation/NSDictionary.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSExtensionRequestHandling } from "../Foundation/NSExtensionRequestHandling.js";
 import type { _NSObject } from "../Foundation/NSObject.js";
 import type { _NSString } from "../Foundation/NSString.js";
@@ -32,7 +34,7 @@ export declare class _FIFinderSync extends _NSObject {
     /** Collaboration, starting in macOS 10.13. */
     supportedServiceNamesForItemWithURL$(itemURL: _NSURL): _NSArray;
     makeListenerEndpointForServiceName$itemURL$andReturnError$(serviceName: NSFileProviderServiceName, itemURL: _NSURL, error: NobjcObject | null): _NSXPCListenerEndpoint | null;
-    valuesForAttributes$forItemWithURL$completion$(attributes: _NSArray, itemURL: _NSURL, completion: NobjcObject | null): void;
+    valuesForAttributes$forItemWithURL$completion$(attributes: _NSArray, itemURL: _NSURL, completion: ((arg0: _NSDictionary, arg1: _NSError) => void) | null): void;
     /**
      * The name of the extension’s toolbar button. To add a toolbar item to the Finder, override the getter method for the toolbar image, name, and tooltip properties.
      */

package/dist/FinderSync/FIFinderSyncController.d.ts

@@ -1,7 +1,7 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "../Foundation/NSArray.js";
 import type { _NSData } from "../Foundation/NSData.js";
 import type { _NSDate } from "../Foundation/NSDate.js";
+import type { _NSError } from "../Foundation/NSError.js";
 import type { _NSExtensionContext } from "../Foundation/NSExtensionContext.js";
 import type { _NSSet } from "../Foundation/NSSet.js";
 import type { _NSString } from "../Foundation/NSString.js";
@@ -38,9 +38,9 @@ export declare class _FIFinderSyncController extends _NSExtensionContext {
     selectedItemURLs(): _NSArray | null;
     /** Collaboration, starting in macOS 10.13. */
     lastUsedDateForItemWithURL$(itemURL: _NSURL): _NSDate | null;
-    setLastUsedDate$forItemWithURL$completion$(lastUsedDate: _NSDate, itemURL: _NSURL, completion: NobjcObject): void;
+    setLastUsedDate$forItemWithURL$completion$(lastUsedDate: _NSDate, itemURL: _NSURL, completion: (error: _NSError) => void): void;
     tagDataForItemWithURL$(itemURL: _NSURL): _NSData | null;
-    setTagData$forItemWithURL$completion$(tagData: _NSData | null, itemURL: _NSURL, completion: NobjcObject): void;
+    setTagData$forItemWithURL$completion$(tagData: _NSData | null, itemURL: _NSURL, completion: (error: _NSError) => void): void;
     /**
      * The directories managed by this extension. The extension receives ``FIFinderSync/beginObservingDirectoryAtURL:`` and ``FIFinderSync/endObservingDirectoryAtURL:`` messages for every directory in this set and for all of their subdirectories. Always set `directoryURLs` when the extension starts. If there are no directories to watch, set `directoryURLs` to an empty set.
      */

package/dist/Foundation/NSArray.d.ts

@@ -65,25 +65,25 @@ export declare class _NSArray extends _NSObject {
     makeObjectsPerformSelector$withObject$(aSelector: string, argument: NobjcObject | null): void;
     objectsAtIndexes$(indexes: _NSIndexSet): _NSArray;
     objectAtIndexedSubscript$(idx: number): NobjcObject;
-    enumerateObjectsUsingBlock$(block: NobjcObject): void;
-    enumerateObjectsWithOptions$usingBlock$(opts: NSEnumerationOptions, block: NobjcObject): void;
-    enumerateObjectsAtIndexes$options$usingBlock$(s: _NSIndexSet, opts: NSEnumerationOptions, block: NobjcObject): void;
-    indexOfObjectPassingTest$(predicate: NobjcObject): number;
-    indexOfObjectWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: NobjcObject): number;
-    indexOfObjectAtIndexes$options$passingTest$(s: _NSIndexSet, opts: NSEnumerationOptions, predicate: NobjcObject): number;
-    indexesOfObjectsPassingTest$(predicate: NobjcObject): _NSIndexSet;
-    indexesOfObjectsWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: NobjcObject): _NSIndexSet;
-    indexesOfObjectsAtIndexes$options$passingTest$(s: _NSIndexSet, opts: NSEnumerationOptions, predicate: NobjcObject): _NSIndexSet;
-    sortedArrayUsingComparator$(cmptr: NobjcObject): _NSArray;
-    sortedArrayWithOptions$usingComparator$(opts: NSSortOptions, cmptr: NobjcObject): _NSArray;
+    enumerateObjectsUsingBlock$(block: (obj: NobjcObject, idx: number, stop: NobjcObject) => void): void;
+    enumerateObjectsWithOptions$usingBlock$(opts: NSEnumerationOptions, block: (obj: NobjcObject, idx: number, stop: NobjcObject) => void): void;
+    enumerateObjectsAtIndexes$options$usingBlock$(s: _NSIndexSet, opts: NSEnumerationOptions, block: (obj: NobjcObject, idx: number, stop: NobjcObject) => void): void;
+    indexOfObjectPassingTest$(predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): number;
+    indexOfObjectWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): number;
+    indexOfObjectAtIndexes$options$passingTest$(s: _NSIndexSet, opts: NSEnumerationOptions, predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): number;
+    indexesOfObjectsPassingTest$(predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
+    indexesOfObjectsWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
+    indexesOfObjectsAtIndexes$options$passingTest$(s: _NSIndexSet, opts: NSEnumerationOptions, predicate: (obj: NobjcObject, idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
+    sortedArrayUsingComparator$(cmptr: (arg0: NobjcObject, arg1: NobjcObject) => number): _NSArray;
+    sortedArrayWithOptions$usingComparator$(opts: NSSortOptions, cmptr: (arg0: NobjcObject, arg1: NobjcObject) => number): _NSArray;
     /** binary search */
-    indexOfObject$inSortedRange$options$usingComparator$(obj: NobjcObject, r: NSRange, opts: NSBinarySearchingOptions, cmp: NobjcObject): number;
+    indexOfObject$inSortedRange$options$usingComparator$(obj: NobjcObject, r: NSRange, opts: NSBinarySearchingOptions, cmp: (arg0: NobjcObject, arg1: NobjcObject) => number): number;
     initWithObjects$(firstObj: NobjcObject): _NSArray;
     initWithArray$(array: _NSArray): _NSArray;
     initWithArray$copyItems$(array: _NSArray, flag: boolean): _NSArray;
     /** Reads array stored in NSPropertyList format from the specified url. */
     initWithContentsOfURL$error$(url: _NSURL, error: NobjcObject | null): _NSArray | null;
-    differenceFromArray$withOptions$usingEquivalenceTest$(other: _NSArray, options: NSOrderedCollectionDifferenceCalculationOptions, block: NobjcObject): _NSOrderedCollectionDifference;
+    differenceFromArray$withOptions$usingEquivalenceTest$(other: _NSArray, options: NSOrderedCollectionDifferenceCalculationOptions, block: (obj1: NobjcObject, obj2: NobjcObject) => boolean): _NSOrderedCollectionDifference;
     differenceFromArray$withOptions$(other: _NSArray, options: NSOrderedCollectionDifferenceCalculationOptions): _NSOrderedCollectionDifference;
     /**
      * Uses isEqual: to determine the difference between the parameter and the receiver

package/dist/Foundation/NSAttributedString.d.ts

@@ -33,8 +33,8 @@ export declare class _NSAttributedString extends _NSObject {
     initWithString$(str: _NSString): _NSAttributedString;
     initWithString$attributes$(str: _NSString, attrs: _NSDictionary | null): _NSAttributedString;
     initWithAttributedString$(attrStr: _NSAttributedString): _NSAttributedString;
-    enumerateAttributesInRange$options$usingBlock$(enumerationRange: NSRange, opts: NSAttributedStringEnumerationOptions, block: NobjcObject): void;
-    enumerateAttribute$inRange$options$usingBlock$(attrName: _NSString, enumerationRange: NSRange, opts: NSAttributedStringEnumerationOptions, block: NobjcObject | null): void;
+    enumerateAttributesInRange$options$usingBlock$(enumerationRange: NSRange, opts: NSAttributedStringEnumerationOptions, block: (attrs: _NSDictionary, range: NSRange, stop: NobjcObject) => void): void;
+    enumerateAttribute$inRange$options$usingBlock$(attrName: _NSString, enumerationRange: NSRange, opts: NSAttributedStringEnumerationOptions, block: ((value: NobjcObject, range: NSRange, stop: NobjcObject) => void) | null): void;
     /**
      * These constructors have a 'baseURL' parameter. If specified, links in the document will be relative to this URL, and images in the document will be looked for relative to this URL (if the other options allow image loading). Defaults to nil. If set to nil, paths will not be resolved.
      */

package/dist/Foundation/NSBackgroundActivityScheduler.d.ts

@@ -1,6 +1,6 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSObject } from "./NSObject.js";
 import type { _NSString } from "./NSString.js";
+import type { NSBackgroundActivityResult } from "./NSBackgroundActivityResult.js";
 import type { NSQualityOfService } from "./NSQualityOfService.js";
 export declare class _NSBackgroundActivityScheduler extends _NSObject {
     static alloc(): _NSBackgroundActivityScheduler;
@@ -13,7 +13,7 @@ export declare class _NSBackgroundActivityScheduler extends _NSObject {
     /**
      * Begin scheduling the activity. All properties should be setup by this point. The block will be called on a serial background queue appropriate for the level of quality of service specified. The system will automatically use NSProcessInfo's -beginActivityWithOptions:reason: API while invoking the block, choosing options appropriate for the desired quality of service. When you are done with the work, be sure to invoke the completionHandler block given to you as an argument to your block. You can pass in a kind of NSBackgroundActivityResult to indicate if the work has been finished or if you are deferring the rest of the work (see -shouldDefer). If you fail to invoke the completionHandler then your activity will never be rescheduled. When invoking the completionHandler, the system will set the schedule the next invocation. If you want to adjust the properties of your scheduler (e.g., the interval or tolerance), do this before invoking the completion block.
      */
-    scheduleWithBlock$(block: NobjcObject): void;
+    scheduleWithBlock$(block: (completionHandler: (arg0: NSBackgroundActivityResult) => void) => void): void;
     /**
      * Stop scheduling the activity. Any currently executing block will still complete.
      */

package/dist/Foundation/NSBlockOperation.d.ts

@@ -4,7 +4,7 @@ export declare class _NSBlockOperation extends _NSOperation {
     static alloc(): _NSBlockOperation;
     static new(): _NSBlockOperation;
     init(): _NSBlockOperation;
-    static blockOperationWithBlock$(block: NobjcObject): _NSBlockOperation;
-    addExecutionBlock$(block: NobjcObject): void;
-    executionBlocks(): NobjcObject;
+    static blockOperationWithBlock$(block: () => void): _NSBlockOperation;
+    addExecutionBlock$(block: () => void): void;
+    executionBlocks(): () => NobjcObject;
 }

package/dist/Foundation/NSBundleResourceRequest.d.ts

@@ -1,5 +1,5 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSBundle } from "./NSBundle.js";
+import type { _NSError } from "./NSError.js";
 import type { _NSObject } from "./NSObject.js";
 import type { _NSProgress } from "./NSProgress.js";
 import type { _NSSet } from "./NSSet.js";
@@ -15,11 +15,11 @@ export declare class _NSBundleResourceRequest extends _NSObject {
     /**
      * Ask the system to fetch the resources that were part of the tag set in this request. Resources will not be purged while in use by the application (as indicated by the application using this begin API paired with a call to -endAccessingResources). If an application has too many fetched resources and the system is unable to reserve enough space for newly requested tags, the request may return an error. When you are finished with the resources and they may be purged off the disk, invoke -endAccessingResources. If the request object is deallocated, it will also inform the system that the resources are no longer in use. The completion block will be invoked on a non-main serial queue when the resources are available or an error has occurred. An example of a possible error that may be reported is the lack of a network connection or a problem connecting to the on-demand servers. Fetch requests are reference counted across the application. So if you have two requests outstanding with the same set of tags, each may be used independently without having to know about any global state. However, each NSBundleResourceRequest object may only be used once. If you cancel an outstanding request (via the cancel method on the NSProgress object, or cancelling a parent progress object you have created) the completion handler argument to this method will be called back with an NSUserCancelledError in the NSCocoaErrorDomain. Be sure to always invoke the -endAccessingResources method to balance a call to the begin method, even in the case of an error in the completion handler. If you want to access the resources again, create a new NSBundleResourceRequest object.
      */
-    beginAccessingResourcesWithCompletionHandler$(completionHandler: NobjcObject | null): void;
+    beginAccessingResourcesWithCompletionHandler$(completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Inform the system that you wish to begin accessing the resources that are part of this request, but do not attempt to download any content over the network. The completion handler will be invoked with a YES argument if the resources are available. If the resources were available, then you must invoke the -endAccessingResources method once you are done accessing them. If the resources were not available, then you may invoke the -beginAccessingResourcesWithCompletionHandler: method to initiate a download of the resources.
      */
-    conditionallyBeginAccessingResourcesWithCompletionHandler$(completionHandler: NobjcObject): void;
+    conditionallyBeginAccessingResourcesWithCompletionHandler$(completionHandler: (resourcesAvailable: boolean) => void): void;
     /**
      * Informs the system that you are finished with the resources that were part of the tag set in this request. Call this after you no longer need the resources to be available on disk. It is important to invoke this method to make room for newly requested resources. This method may only be invoked if you have received a callback from -beginAccessingResourcesWithCompletionHandler:. To cancel an in-progress request, invoke cancel on the -progress property.
      */

package/dist/Foundation/NSCalendar.d.ts

@@ -102,7 +102,7 @@ export declare class _NSCalendar extends _NSObject {
     /**
      * This method computes the dates which match (or most closely match) a given set of components, and calls the block once for each of them, until the enumeration is stopped. There will be at least one intervening date which does not match all the components (or the given date itself must not match) between the given date and any result. If the NSCalendarSearchBackwards option is used, this method finds the previous match before the given date. The intent is that the same matches as for a forwards search will be found (that is, if you are enumerating forwards or backwards for each hour with minute "27", the seconds in the date you will get in forwards search would obviously be 00, and the same will be true in a backwards search in order to implement this rule. Similarly for DST backwards jumps which repeats times, you'll get the first match by default, where "first" is defined from the point of view of searching forwards. So, when searching backwards looking for a particular hour, with no minute and second specified, you don't get a minute and second of 59:59 for the matching hour (which would be the nominal first match within a given hour, given the other rules here, when searching backwards). If the NSCalendarMatchStrictly option is used, the algorithm travels as far forward or backward as necessary looking for a match, but there are ultimately implementation-defined limits in how far distant the search will go. If the NSCalendarMatchStrictly option is not specified, the algorithm searches up to the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument. If you want to find the next Feb 29 in the Gregorian calendar, for example, you have to specify the NSCalendarMatchStrictly option to guarantee finding it. If an exact match is not possible, and requested with the NSCalendarMatchStrictly option, nil is passed to the block and the enumeration ends. (Logically, since an exact match searches indefinitely into the future, if no match is found there's no point in continuing the enumeration.) If the NSCalendarMatchStrictly option is NOT used, exactly one option from the set {NSCalendarMatchPreviousTimePreservingSmallerUnits, NSCalendarMatchNextTimePreservingSmallerUnits, NSCalendarMatchNextTime} must be specified, or an illegal argument exception will be thrown. If the NSCalendarMatchPreviousTimePreservingSmallerUnits option is specified, and there is no matching time before the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument, the method will return the previous existing value of the missing unit and preserves the lower units' values (e.g., no 2:37am results in 1:37am, if that exists). If the NSCalendarMatchNextTimePreservingSmallerUnits option is specified, and there is no matching time before the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument, the method will return the next existing value of the missing unit and preserves the lower units' values (e.g., no 2:37am results in 3:37am, if that exists). If the NSCalendarMatchNextTime option is specified, and there is no matching time before the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument, the method will return the next existing time which exists (e.g., no 2:37am results in 3:00am, if that exists). If the NSCalendarMatchFirst option is specified, and there are two or more matching times (all the components are the same, including isLeapMonth) before the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument, the method will return the first occurrence. If the NSCalendarMatchLast option is specified, and there are two or more matching times (all the components are the same, including isLeapMonth) before the end of the next instance of the next higher unit to the highest specified unit in the NSDateComponents argument, the method will return the last occurrence. If neither the NSCalendarMatchFirst or NSCalendarMatchLast option is specified, the default behavior is to act as if NSCalendarMatchFirst was specified. There is no option to return middle occurrences of more than two occurrences of a matching time, if such exist. Result dates have an integer number of seconds (as if 0 was specified for the nanoseconds property of the NSDateComponents matching parameter), unless a value was set in the nanoseconds property, in which case the result date will have that number of nanoseconds (or as close as possible with floating point numbers). The enumeration is stopped by setting *stop = YES in the block and return. It is not necessary to set *stop to NO to keep the enumeration going.
      */
-    enumerateDatesStartingAfterDate$matchingComponents$options$usingBlock$(start: _NSDate, comps: _NSDateComponents, opts: NSCalendarOptions, block: NobjcObject | null): void;
+    enumerateDatesStartingAfterDate$matchingComponents$options$usingBlock$(start: _NSDate, comps: _NSDateComponents, opts: NSCalendarOptions, block: ((date: _NSDate, exactMatch: boolean, stop: NobjcObject) => void) | null): void;
     /**
      * This method computes the next date which matches (or most closely matches) a given set of components. The general semantics follow those of the -enumerateDatesStartingAfterDate:... method above. To compute a sequence of results, use the -enumerateDatesStartingAfterDate:... method above, rather than looping and calling this method with the previous loop iteration's result.
      */

package/dist/Foundation/NSData.d.ts

@@ -44,11 +44,11 @@ export declare class _NSData extends _NSObject {
     /**
      * 'block' is called once for each contiguous region of memory in the receiver (once total for contiguous NSDatas), until either all bytes have been enumerated, or the 'stop' parameter is set to YES.
      */
-    enumerateByteRangesUsingBlock$(block: NobjcObject): void;
+    enumerateByteRangesUsingBlock$(block: (bytes: NobjcObject, byteRange: NSRange, stop: NobjcObject) => void): void;
     initWithBytes$length$(bytes: Uint8Array | null, length: number): _NSData;
     initWithBytesNoCopy$length$(bytes: Uint8Array, length: number): _NSData;
     initWithBytesNoCopy$length$freeWhenDone$(bytes: Uint8Array, length: number, b: boolean): _NSData;
-    initWithBytesNoCopy$length$deallocator$(bytes: Uint8Array, length: number, deallocator: NobjcObject | null): _NSData;
+    initWithBytesNoCopy$length$deallocator$(bytes: Uint8Array, length: number, deallocator: ((bytes: NobjcObject, length: number) => void) | null): _NSData;
     initWithContentsOfFile$options$error$(path: _NSString, readOptionsMask: NSDataReadingOptions, errorPtr: NobjcObject | null): _NSData | null;
     initWithContentsOfURL$options$error$(url: _NSURL, readOptionsMask: NSDataReadingOptions, errorPtr: NobjcObject | null): _NSData | null;
     initWithContentsOfFile$(path: _NSString): _NSData | null;

package/dist/Foundation/NSDictionary.d.ts

@@ -53,12 +53,12 @@ export declare class _NSDictionary extends _NSObject {
     /** count refers to the number of elements in the dictionary */
     getObjects$andKeys$count$(objects: NobjcObject | null, keys: NobjcObject | null, count: number): void;
     objectForKeyedSubscript$(key: NobjcObject): NobjcObject | null;
-    enumerateKeysAndObjectsUsingBlock$(block: NobjcObject): void;
-    enumerateKeysAndObjectsWithOptions$usingBlock$(opts: NSEnumerationOptions, block: NobjcObject): void;
-    keysSortedByValueUsingComparator$(cmptr: NobjcObject): _NSArray;
-    keysSortedByValueWithOptions$usingComparator$(opts: NSSortOptions, cmptr: NobjcObject): _NSArray;
-    keysOfEntriesPassingTest$(predicate: NobjcObject): _NSSet;
-    keysOfEntriesWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: NobjcObject): _NSSet;
+    enumerateKeysAndObjectsUsingBlock$(block: (key: NobjcObject, obj: NobjcObject, stop: NobjcObject) => void): void;
+    enumerateKeysAndObjectsWithOptions$usingBlock$(opts: NSEnumerationOptions, block: (key: NobjcObject, obj: NobjcObject, stop: NobjcObject) => void): void;
+    keysSortedByValueUsingComparator$(cmptr: (arg0: NobjcObject, arg1: NobjcObject) => number): _NSArray;
+    keysSortedByValueWithOptions$usingComparator$(opts: NSSortOptions, cmptr: (arg0: NobjcObject, arg1: NobjcObject) => number): _NSArray;
+    keysOfEntriesPassingTest$(predicate: (key: NobjcObject, obj: NobjcObject, stop: NobjcObject) => boolean): _NSSet;
+    keysOfEntriesWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: (key: NobjcObject, obj: NobjcObject, stop: NobjcObject) => boolean): _NSSet;
     /**
      * This method is unsafe because it could potentially cause buffer overruns. You should use -getObjects:andKeys:count:
      * @deprecated Use -getObjects:andKeys:count: instead

package/dist/Foundation/NSError.d.ts

@@ -13,8 +13,8 @@ export declare class _NSError extends _NSObject {
     /**
      * Specify a block which will be called from the implementations of localizedDescription, localizedFailureReason, localizedRecoverySuggestion, localizedRecoveryOptions, recoveryAttempter, helpAnchor, and debugDescription when the underlying value for these is not present in the userInfo dictionary of NSError instances with the specified domain. The provider will be called with the userInfo key corresponding to the queried property: For instance, NSLocalizedDescriptionKey for localizedDescription. The provider should return nil for any keys it is not able to provide and, very importantly, any keys it does not recognize (since we may extend the list of keys in future releases). The specified block will be called synchronously at the time when the above properties are queried. The results are not cached. This provider is optional. It enables localization and formatting of error messages to be done lazily; rather than populating the userInfo at NSError creation time, these keys will be fetched on-demand when asked for. It is expected that only the “owner” of an NSError domain specifies the provider for the domain, and this is done once. This facility is not meant for consumers of errors to customize the userInfo entries. This facility should not be used to customize the behaviors of error domains provided by the system. If an appropriate result for the requested key cannot be provided, return nil rather than choosing to manufacture a generic fallback response such as "Operation could not be completed, error 42." NSError will take care of the fallback cases.
      */
-    static setUserInfoValueProviderForDomain$provider$(errorDomain: _NSString, provider: NobjcObject | null): void;
-    static userInfoValueProviderForDomain$(errorDomain: _NSString): NobjcObject | null;
+    static setUserInfoValueProviderForDomain$provider$(errorDomain: _NSString, provider: ((err: _NSError, userInfoKey: _NSString) => NobjcObject) | null): void;
+    static userInfoValueProviderForDomain$(errorDomain: _NSString): ((arg0: _NSError, arg1: _NSString) => NobjcObject) | null;
     /** Domain cannot be nil; dict may be nil if no userInfo desired. */
     initWithDomain$code$userInfo$(domain: _NSString, code: number, dict: _NSDictionary | null): _NSError;
     /**

package/dist/Foundation/NSExpression.d.ts

@@ -54,7 +54,7 @@ export declare class _NSExpression extends _NSObject {
     /**
      * Expression that invokes the block with the parameters; note that block expressions are not encodable or representable as parseable strings.
      */
-    static expressionForBlock$arguments$(block: NobjcObject | null, arguments_: _NSArray | null): _NSExpression;
+    static expressionForBlock$arguments$(block: ((evaluatedObject: NobjcObject, expressions: _NSArray, context: _NSMutableDictionary) => NobjcObject) | null, arguments_: _NSArray | null): _NSExpression;
     /**
      * Expression that will return the result of trueExpression or falseExpression depending on the value of predicate
      */
@@ -95,7 +95,7 @@ export declare class _NSExpression extends _NSObject {
      * expression which will be evaluated if a conditional expression's predicate evaluates to false
      */
     falseExpression(): _NSExpression;
-    expressionBlock(): NobjcObject | null;
+    expressionBlock(): ((arg0: NobjcObject, arg1: _NSArray, arg2: _NSMutableDictionary) => NobjcObject) | null;
 }
 export interface _NSExpression extends _NSCopying {
 }

package/dist/Foundation/NSExtensionContext.d.ts

@@ -1,4 +1,3 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "./NSArray.js";
 import type { _NSError } from "./NSError.js";
 import type { _NSObject } from "./NSObject.js";
@@ -10,13 +9,13 @@ export declare class _NSExtensionContext extends _NSObject {
     /**
      * Signals the host to complete the app extension request with the supplied result items. The completion handler optionally contains any work which the extension may need to perform after the request has been completed, as a background-priority task. The `expired` parameter will be YES if the system decides to prematurely terminate a previous non-expiration invocation of the completionHandler. Note: calling this method will eventually dismiss the associated view controller.
      */
-    completeRequestReturningItems$completionHandler$(items: _NSArray | null, completionHandler: NobjcObject | null): void;
+    completeRequestReturningItems$completionHandler$(items: _NSArray | null, completionHandler: ((expired: boolean) => void) | null): void;
     /**
      * Signals the host to cancel the app extension request, with the supplied error, which should be non-nil. The userInfo of the NSError will contain a key NSExtensionItemsAndErrorsKey which will have as its value a dictionary of NSExtensionItems and associated NSError instances.
      */
     cancelRequestWithError$(error: _NSError): void;
     /** Asks the host to open a URL on the extension's behalf */
-    openURL$completionHandler$(URL: _NSURL, completionHandler: NobjcObject | null): void;
+    openURL$completionHandler$(URL: _NSURL, completionHandler: ((success: boolean) => void) | null): void;
     /**
      * The list of input NSExtensionItems associated with the context. If the context has no input items, this array will be empty.
      */

package/dist/Foundation/NSFileCoordinator.d.ts

@@ -1,5 +1,6 @@
 import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "./NSArray.js";
+import type { _NSError } from "./NSError.js";
 import type { _NSFilePresenter } from "./NSFilePresenter.js";
 import type { _NSObject } from "./NSObject.js";
 import type { _NSOperationQueue } from "./NSOperationQueue.js";
@@ -25,18 +26,18 @@ export declare class _NSFileCoordinator extends _NSObject {
     /**
      * Given an array of one or more NSFileAccessIntent objects that specify reading and/or writing items located by the corresponding URLs, wait asynchronously for certain other readers and writers and then invoke the passed-in block on the given queue, which must not be nil. If an error occurs, file access is not granted and a non-nil error will be passed to the accessor block. If file access is successfully granted, then 'error' will be nil and you may perform the intended file access inside the accessor block. You must use the URL property on the NSFileAccessIntent objects when performing file access in the accessor block. Within the block, the NSFileAccessIntent objects' URLs may differ from their original values to account for items that have been moved or renamed while waiting for access to be granted. When access to the intended files is granted, certain other readers and writers are made to wait until the given block returns, which defines the end of that file access. Do not allow file access to continue after the accessor block returns by dispatching work to other threads or queues. You can invoke this method to serialize your process's access of files and directories with other processes' access of the same files and directories so that inconsistencies due to overlapping reading and writing don't occur. It also causes messages to be sent to NSFilePresenters, and wait for NSFilePresenters to react, as described below. The fact that file system items can be moved or renamed while this method is waiting to invoke the block you passed when invoking it is why it's critical to use the URL property on the NSFileAccessIntent objects, not the URLs you used when initializing them. In general a coordinated reader waits for a coordinated writer of the same item, and a coordinated writer waits for coordinated readers and other coordinated writers of the same item. Coordinated readers do not wait for each other. Coordinated reading or writing of items in a file package is treated as coordinated reading or writing of the file package as a whole. A coordinated reader of a directory that is not a file package does not wait for coordinated writers of contained items, or cause such writers to wait. With one exception, a coordinated writer of a directory that is not a file package does not wait for coordinated readers and writers of contained items, or cause such readers and writers to wait. The exception is when you use NSFileCoordinatorWritingForDeleting, NSFileCoordinatorWritingForMoving, or NSFileCoordinatorWritingForReplacing. They make your coordinated writer wait for previously scheduled coordinated readers and writers of contained items, and causes subsequently scheduled coordinated readers and writers of contained items to wait. None of those rules apply to coordinated readers and writers that are using the exact same instance of NSFileCoordinator, including arrays of multiple NSFileAccessIntent objects. Instances of NSFileCoordinator never block themselves. You can take advantage of that in a couple of ways when invoking -coordinateAccessWithIntents:queue:byAccessor: multiple times on the same NSFileCoordinator instance, but take care because doing so raises the possibility of deadlocking with other processes that are doing the same sort of thing. If you can, you should invoke -coordinateAccessWithIntents:queue:byAccessor: a single time with multiple NSFileAccessIntent objects instead of invoking it multiple times with a single NSFileAccssIntent object. In addition to waiting for writers, readers wait for NSFilePresenters that are messaged as part of the coordinated reading. Coordinated reading of an item triggers the sending of messages to NSFilePresenters that implement the corresponding optional methods, even those in other processes, except the one specified when -initWithFilePresenter: was invoked: - -relinquishPresentedItemToReader: is sent to NSFilePresenters of the item and, if the item is in a file package, NSFilePresenters of the file package. If there are nested file packages then the message is sent to NSFilePresenters of all of them. - If NSFileCoordinatorReadingWithoutChanges is not used then -savePresentedItemChangesWithCompletionHandler: is also sent to the same NSFilePresenters. In addition to waiting for readers and other writers, writers wait for NSFilePresenters that are messaged as part of the coordinated writing. Coordinated writing of an item triggers the sending of messages to NSFilePresenters that implement the corresponding optional methods, even those in other processes, except the one specified when -initWithFilePresenter: was invoked: - -relinquishPresentedItemToWriter: is sent to NSFilePresenters of the item and, if the item is in a file package, NSFilePresenters of the file package. If there are nested file packages then the message is sent to NSFilePresenters of all of them. - If NSFileCoordinatorWritingForDeleting, NSFileCoordinatorWritingForMoving, or NSFileCoordinatorWritingForReplacing is used and the item is a directory then -relinquishPresentedItemToWriter: is also sent to NSFilePresenters of each item contained by it. - If NSFileCoordinatorWritingForDeleting or NSFileCoordinatorWritingForReplacing is used then -accommodatePresentedItemDeletionWithCompletionHandler: is sent to NSFilePresenters of the item and, if the item is a directory, NSFilePresenters of each item contained by it. -accommodatePresentedSubitemDeletionAtURL:completionHandler: is sent to NSFilePresenters of each file package that contains the item. - When NSFileCoordinatorWritingForReplacing is used the the definition of "the item" depends on what happened while waiting for other writers. See the description of it above. - If NSFileCoordinatorWritingForMerging is used then -savePresentedItemChangesWithCompletionHandler: is sent to NSFilePresenters of the item and, if the item is in a file package, NSFilePresenters of the file package. If there are nested file packages then the message is sent to NSFilePresenters of all of them. For both coordinated reading and writing, if there are multiple NSFilePresenters involved then the order in which they are messaged is undefined. If an NSFilePresenter signals failure then waiting will fail and *outError will be set to an NSError describing the failure.
      */
-    coordinateAccessWithIntents$queue$byAccessor$(intents: _NSArray, queue: _NSOperationQueue, accessor: NobjcObject | null): void;
+    coordinateAccessWithIntents$queue$byAccessor$(intents: _NSArray, queue: _NSOperationQueue, accessor: ((error: _NSError) => void) | null): void;
     /**
      * The next four methods behave similarly to -coordinateAccessWithIntents:queue:byAccessor: with one or two NSFileAccessIntent objects with the following exceptions: Each of these methods wait synchronously on the same thread they were invoked on before invoking the passed-in accessor block on the same thread, instead of waiting asynchronously and scheduling invocation of the block on a specific queue. The accessor block of each of these methods is passed one or more URLs that locate the intended items, perhaps changed from the original URLs to take into account the fact that the item might have been moved or renamed during the waiting. Each of these methods returns an NSError by reference instead of passing it to the accessory block. However, these methods are uncommon among Cocoa framework methods in that they don't also return a result indicating success or failure. The success of the waiting that they do is typically not interesting to invokers. Only the success of file system access done by the passed-in block is interesting. (The failure of either is of course interesting.) When invoking these methods it's cleanest to just declare a __block variable outside of the block and initialize it to a value that signals failure, and then inside the block set it to a value that signals success. If the waiting fails then the invoked method sets the error reference to an NSError that describes what went wrong, your block will not be invoked, your __block variable will not be set to a value that signals success, and all will be as it should be, with failure signaled and an NSError that describes the failure.
      */
-    coordinateReadingItemAtURL$options$error$byAccessor$(url: _NSURL, options: NSFileCoordinatorReadingOptions, outError: NobjcObject | null, reader: NobjcObject): void;
-    coordinateWritingItemAtURL$options$error$byAccessor$(url: _NSURL, options: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, writer: NobjcObject): void;
-    coordinateReadingItemAtURL$options$writingItemAtURL$options$error$byAccessor$(readingURL: _NSURL, readingOptions: NSFileCoordinatorReadingOptions, writingURL: _NSURL, writingOptions: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, readerWriter: NobjcObject): void;
-    coordinateWritingItemAtURL$options$writingItemAtURL$options$error$byAccessor$(url1: _NSURL, options1: NSFileCoordinatorWritingOptions, url2: _NSURL, options2: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, writer: NobjcObject): void;
+    coordinateReadingItemAtURL$options$error$byAccessor$(url: _NSURL, options: NSFileCoordinatorReadingOptions, outError: NobjcObject | null, reader: (newURL: _NSURL) => void): void;
+    coordinateWritingItemAtURL$options$error$byAccessor$(url: _NSURL, options: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, writer: (newURL: _NSURL) => void): void;
+    coordinateReadingItemAtURL$options$writingItemAtURL$options$error$byAccessor$(readingURL: _NSURL, readingOptions: NSFileCoordinatorReadingOptions, writingURL: _NSURL, writingOptions: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, readerWriter: (newReadingURL: _NSURL, newWritingURL: _NSURL) => void): void;
+    coordinateWritingItemAtURL$options$writingItemAtURL$options$error$byAccessor$(url1: _NSURL, options1: NSFileCoordinatorWritingOptions, url2: _NSURL, options2: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, writer: (newURL1: _NSURL, newURL2: _NSURL) => void): void;
     /**
      * Prepare to more efficiently do a large number of invocations of -coordinate... methods, first synchronously messaging and waiting for NSFilePresenters in a variation of what individual invocations of the -coordinate... methods would do, and then, if no error occurs, invoke the passed-in block. The passed-in block must invoke the completion handler passed to it when all of the coordinated reading and writing it does is done. The completion handler block can be invoked on any thread (or from any dispatch queue, if that's how you think of it). This method returns errors in the same manner as the -coordinate... methods. The -coordinate... methods must use interprocess communication to message instances of NSFileCoordinator and NSFilePresenter in other processes in the system. That is an expense best avoided when reading or writing many files in one operation. Using this method can greatly reduce the amount of interprocess communication required by, for example, a large batched copying or moving of files. You use it by moving all of the invocations of the -coordinate... methods your application will do during a batch operation, or the scheduling of them if the operation's work is done in a multithreaded fashion, into a block and passing that block to an invocation of this method, remembering that the completion handler passed to that block must be invoked when the operation is done. You don't simply pass all URLs that will be passed into invocations of the -coordinate... methods when invoking this method. Instead you pass the top-level files and directories involved in the operation. This method triggers messages to not just NSFilePresenters of those items, but also NSFilePresenters of items contained by those items. For example, when Finder uses this method during a copy operation readingURLs is an array of the URLs of the exact files and folders that the user has selected, even though those folders may contain many files and subfolders for which Finder is going to do coordinated reading, and writingURLs is an array that contains just the URL of the destination folder. In most cases it is redundant to pass the same reading or writing options in an invocation of this method as are passed to individual invocations of the -coordinate... methods invoked by the block passed to an invocation of this method. For example, when Finder invokes this method during a copy operation it does not pass NSFileCoordinatorReadingWithoutChanges because it is appropriate to trigger the saving of document changes right away, but it does pass it when doing the nested invocations of -coordinate... methods because it is not necessary to trigger saving again, even if the user changes the document before the Finder proceeds far enough to actually copy that document's file.
      */
-    prepareForReadingItemsAtURLs$options$writingItemsAtURLs$options$error$byAccessor$(readingURLs: _NSArray, readingOptions: NSFileCoordinatorReadingOptions, writingURLs: _NSArray, writingOptions: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, batchAccessor: NobjcObject): void;
+    prepareForReadingItemsAtURLs$options$writingItemsAtURLs$options$error$byAccessor$(readingURLs: _NSArray, readingOptions: NSFileCoordinatorReadingOptions, writingURLs: _NSArray, writingOptions: NSFileCoordinatorWritingOptions, outError: NobjcObject | null, batchAccessor: (arg0: () => void) => void): void;
     /**
      * Announce that the item located by a URL is going to be located by another URL. Support for App Sandbox on OS X. Some applications can rename files while saving them. For example, when a user adds attachments to a rich text document, TextEdit changes the document's extension from .rtf to .rtfd. A sandboxed application like TextEdit must ordinarily prompt the user for approval before renaming a document. You can invoke this method to make your process declare its intent to rename a document without user approval. After the renaming succeeds you must invoke -itemAtURL:didMoveToURL:, with the same arguments, for the process to keep access to the file with its new name and to give up access to any file that appears with the old name. If the renaming fails you should probably not invoke -itemAtURL:didMoveToURL:. There is no reason to invoke this method from applications that do not use App Sandbox. Invoking it does nothing on iOS.
      */

package/dist/Foundation/NSFileHandle.d.ts

@@ -59,10 +59,10 @@ export declare class _NSFileHandle extends _NSObject {
     /** @deprecated closeAndReturnError: */
     closeFile(): void;
     availableData(): _NSData;
-    readabilityHandler(): NobjcObject | null;
-    setReadabilityHandler$(value: NobjcObject | null): void;
-    writeabilityHandler(): NobjcObject | null;
-    setWriteabilityHandler$(value: NobjcObject | null): void;
+    readabilityHandler(): ((arg0: _NSFileHandle) => void) | null;
+    setReadabilityHandler$(value: ((arg0: _NSFileHandle) => void) | null): void;
+    writeabilityHandler(): ((arg0: _NSFileHandle) => void) | null;
+    setWriteabilityHandler$(value: ((arg0: _NSFileHandle) => void) | null): void;
     fileDescriptor(): number;
     /** @deprecated getOffset:error: */
     offsetInFile(): number;

package/dist/Foundation/NSFileManager.d.ts

@@ -5,7 +5,9 @@ import type { _NSCopying } from "./NSCopying.js";
 import type { _NSData } from "./NSData.js";
 import type { _NSDictionary } from "./NSDictionary.js";
 import type { _NSDirectoryEnumerator } from "./NSDirectoryEnumerator.js";
+import type { _NSError } from "./NSError.js";
 import type { _NSFileManagerDelegate } from "./NSFileManagerDelegate.js";
+import type { _NSFileVersion } from "./NSFileVersion.js";
 import type { _NSObject } from "./NSObject.js";
 import type { _NSString } from "./NSString.js";
 import type { _NSURL } from "./NSURL.js";
@@ -30,7 +32,7 @@ export declare class _NSFileManager extends _NSObject {
     /**
      * This method starts the process of unmounting the volume specified by url. If the volume is encrypted, it is re-locked after being unmounted. The completionHandler will be executed when the operation is complete. If the operation was successful, the block’s errorOrNil argument will be nil; otherwise, errorOrNil will be an error object indicating why the unmount operation failed.
      */
-    unmountVolumeAtURL$options$completionHandler$(url: _NSURL, mask: NSFileManagerUnmountOptions, completionHandler: NobjcObject | null): void;
+    unmountVolumeAtURL$options$completionHandler$(url: _NSURL, mask: NSFileManagerUnmountOptions, completionHandler: ((errorOrNil: _NSError) => void) | null): void;
     /**
      * -contentsOfDirectoryAtURL:includingPropertiesForKeys:options:error: returns an NSArray of NSURLs identifying the the directory entries. If this method returns nil, an NSError will be returned by reference in the 'error' parameter. If the directory contains no entries, this method will return the empty array. When an array is specified for the 'keys' parameter, the specified property values will be pre-fetched and cached with each enumerated URL. This method always does a shallow enumeration of the specified directory (i.e. it always acts as if NSDirectoryEnumerationSkipsSubdirectoryDescendants has been specified). If you need to perform a deep enumeration, use -[NSFileManager enumeratorAtURL:includingPropertiesForKeys:options:errorHandler:]. If you wish to only receive the URLs and no other attributes, then pass '0' for 'options' and an empty NSArray ('[NSArray array]') for 'keys'. If you wish to have the property caches of the vended URLs pre-populated with a default set of attributes, then pass '0' for 'options' and 'nil' for 'keys'.
      */
@@ -166,7 +168,7 @@ export declare class _NSFileManager extends _NSObject {
     /**
      * enumeratorAtURL:includingPropertiesForKeys:options:errorHandler: returns an NSDirectoryEnumerator rooted at the provided directory URL. The NSDirectoryEnumerator returns NSURLs from the -nextObject method. The optional 'includingPropertiesForKeys' parameter indicates which resource properties should be pre-fetched and cached with each enumerated URL. The optional 'errorHandler' block argument is invoked when an error occurs. Parameters to the block are the URL on which an error occurred and the error. When the error handler returns YES, enumeration continues if possible. Enumeration stops immediately when the error handler returns NO. If you wish to only receive the URLs and no other attributes, then pass '0' for 'options' and an empty NSArray ('[NSArray array]') for 'keys'. If you wish to have the property caches of the vended URLs pre-populated with a default set of attributes, then pass '0' for 'options' and 'nil' for 'keys'.
      */
-    enumeratorAtURL$includingPropertiesForKeys$options$errorHandler$(url: _NSURL, keys: _NSArray | null, mask: NSDirectoryEnumerationOptions, handler: NobjcObject | null): _NSDirectoryEnumerator | null;
+    enumeratorAtURL$includingPropertiesForKeys$options$errorHandler$(url: _NSURL, keys: _NSArray | null, mask: NSDirectoryEnumerationOptions, handler: ((url: _NSURL, error: _NSError) => boolean) | null): _NSDirectoryEnumerator | null;
     /**
      * subpathsAtPath: returns an NSArray of all contents and subpaths recursively from the provided path. This may be very expensive to compute for deep filesystem hierarchies, and should probably be avoided.
      */
@@ -213,23 +215,23 @@ export declare class _NSFileManager extends _NSObject {
     /**
      * Asynchronously pauses sync of an item at the given URL. Call this when opening an item to prevent sync from altering the contents of the URL. Once paused, the file provider will not upload local changes nor download remote changes. While paused, call ``uploadLocalVersionOfUbiquitousItem(at:withConflictResolutionPolicy:completionHandler:)`` when the document is in a stable state. This action keeps the server version as up-to-date as possible. If the item is already paused, a second call to this method reports success. If the file provider is already applying changes to the item, the pause fails with an ``NSFileWriteUnknownError-enum.case``, with an underlying error that has domain ``NSPOSIXErrorDomain`` and code ``POSIXError/EBUSY``. If the pause fails, wait for the state to stabilize before retrying. Pausing also fails with ``CocoaError/featureUnsupported`` if `url` refers to a regular (non-package) directory. Pausing sync is independent of the calling app's lifecycle; sync doesn't automatically resume if the app closes or crashes and relaunches later. To resume syncing, explicitly call ``resumeSyncForUbiquitousItem(at:with:completionHandler:)``. Always be sure to resume syncing before you close the item. - Parameters: - url: The URL of the item for which to pause sync. - completionHandler: A closure or block that the framework calls when the pause action completes. It receives a single ``NSError`` parameter to indicate an error that prevented pausing; this value is `nil` if the pause succeeded. In Swift, you can omit the completion handler and catch the thrown error instead.
      */
-    pauseSyncForUbiquitousItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    pauseSyncForUbiquitousItemAtURL$completionHandler$(url: _NSURL, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Asynchronously resumes the sync on a paused item using the given resume behavior. Always call this method when your app closes an item to allow the file provider to sync local changes back to the server. In most situations, the ``NSFileManagerResumeSyncBehavior/preserveLocalChanges`` behavior is the best choice to avoid any risk of data loss. The resume call fails with ``CocoaError/featureUnsupported`` if `url` isn't currently paused. If the device isn't connected to the network, the call may fail with ``NSFileWriteUnknownError-enum.case``, with the underlying error of <doc://com.apple.documentation/documentation/FileProvider/NSFileProviderError/serverUnreachable>. - Parameters: - url: The URL of the item for which to resume sync. - behavior: A ``NSFileManagerResumeSyncBehavior`` value that tells the file manager how to handle conflicts between local and remote versions of files. - completionHandler: A closure or block that the framework calls when the resume action completes. It receives a single ``NSError`` parameter to indicate an error that prevented the resume action; the value is `nil` if the resume succeeded. In Swift, you can omit the completion handler and catch the thrown error instead.
      */
-    resumeSyncForUbiquitousItemAtURL$withBehavior$completionHandler$(url: _NSURL, behavior: NSFileManagerResumeSyncBehavior, completionHandler: NobjcObject | null): void;
+    resumeSyncForUbiquitousItemAtURL$withBehavior$completionHandler$(url: _NSURL, behavior: NSFileManagerResumeSyncBehavior, completionHandler: ((error: _NSError) => void) | null): void;
     /**
      * Asynchronously fetches the latest remote version of a given item from the server. Use this method if uploading fails due to a version conflict and sync is paused. In this case, fetching the latest remote version allows you to inspect the newer item from the server, resolve the conflict, and resume uploading. The version provided by this call depends on several factors: * If there is no newer version of the file on the server, the caller receives the current version of the file. * If the server has a newer version and sync isn't paused, this call replaces the local item and provides the version of the new item. * If the server has a newer version but sync is paused, the returned version points to a side location. In this case, call ``NSFileVersion/replaceItem(at:options:)`` on the provided version object to replace the local item with the newer item from the server. If the device isn't connected to the network, the call may fail with ``NSFileReadUnknownError-enum.case``, with the underlying error of <doc://com.apple.documentation/documentation/FileProvider/NSFileProviderError/serverUnreachable>. - Parameters: - url: The URL of the item for which to check the version. - completionHandler: A closure or block that the framework calls when the fetch action completes. It receives parameters of types ``NSFileVersion`` and ``NSError``. The error is `nil` if fetching the remote version succeeded; otherwise it indicates the error that caused the call to fail. In Swift, you can omit the completion handler, catching any error in a `do`-`catch` block and receiving the version as the return value.
      */
-    fetchLatestRemoteVersionOfItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    fetchLatestRemoteVersionOfItemAtURL$completionHandler$(url: _NSURL, completionHandler: ((latestRemoteVersion: _NSFileVersion, error: _NSError) => void) | null): void;
     /**
      * Asynchronously uploads the local version of the item using the provided conflict resolution policy. Once your app pauses a sync for an item, call this method every time your document is in a stable state. This action keeps the server version as up-to-date as possible. If the server has a newer version than the one to which the app made changes, uploading fails with ``NSFileWriteUnknownError-enum.case``, with an underlying error of <doc://com.apple.documentation/documentation/FileProvider/NSFileProviderError/localVersionConflictingWithServer>. In this case, call ``FileManager/fetchLatestRemoteVersionOfItem(at:completionHandler:)``, rebase local changes on top of that version, and retry the upload. If the device isn't connected to the network, the call may fail with ``NSFileWriteUnknownError-enum.case``, with the underlying error of <doc://com.apple.documentation/documentation/FileProvider/NSFileProviderError/serverUnreachable>. - Parameters: - url: The URL of the item for which to check the version. - conflictResolutionPolicy: The policy the file manager applies if the local and server versions conflict. - completionHandler: A closure or block that the framework calls when the upload completes. It receives parameters of types ``NSFileVersion`` and ``NSError``. The error is `nil` if fetching the remote version succeeded; otherwise it indicates the error that caused the call to fail. In Swift, you can omit the completion handler, catching any error in a `do`-`catch` block and receiving the version as the return value.
      */
-    uploadLocalVersionOfUbiquitousItemAtURL$withConflictResolutionPolicy$completionHandler$(url: _NSURL, conflictResolutionPolicy: NSFileManagerUploadLocalVersionConflictPolicy, completionHandler: NobjcObject | null): void;
+    uploadLocalVersionOfUbiquitousItemAtURL$withConflictResolutionPolicy$completionHandler$(url: _NSURL, conflictResolutionPolicy: NSFileManagerUploadLocalVersionConflictPolicy, completionHandler: ((uploadedVersion: _NSFileVersion, error: _NSError) => void) | null): void;
     /**
      * Asynchronously returns a dictionary of zero or more NSFileProviderService instances, which enable your application to instruct the file's provider to take various actions on or with regards to the given URL. To do this, first identify an NSFileProviderService object whose name matches the service you wish to use. Then get an NSXPCConnection from it and set up its NSXPCInterface with the protocol that matches the service's name. You'll need to refer to external documentation or an SDK supplied by the provider to get this information. Once an NSXPCConnection is obtained, you must finish configuring it and send it -resume. Failure to do so will result in leaking system resources.
      */
-    getFileProviderServicesForItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    getFileProviderServicesForItemAtURL$completionHandler$(url: _NSURL, completionHandler: ((services: _NSDictionary, error: _NSError) => void) | null): void;
     /** Available for OS X in 10.8.3. */
     containerURLForSecurityApplicationGroupIdentifier$(groupIdentifier: _NSString): _NSURL | null;
     homeDirectoryForUser$(userName: _NSString): _NSURL | null;

package/dist/Foundation/NSFilePresenter.d.ts

@@ -1,4 +1,4 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSError } from "./NSError.js";
 import type { _NSFileVersion } from "./NSFileVersion.js";
 import type { _NSOperationQueue } from "./NSOperationQueue.js";
 import type { _NSSet } from "./NSSet.js";
@@ -7,23 +7,23 @@ export interface _NSFilePresenter {
     /**
      * Given that something in the system is waiting to read from the presented file or directory, do whatever it takes to ensure that the application will behave properly while that reading is happening, and then invoke the completion handler. The definition of "properly" depends on what kind of ownership model the application implements. Implementations of this method must always invoke the passed-in reader block because other parts of the system will wait until it is invoked or until the user loses patience and cancels the waiting. When an implementation of this method invokes the passed-in block it can pass that block yet another block, which will be invoked in the receiver's operation queue when reading is complete. A common sequence that your NSFilePresenter must handle is the file coordination mechanism sending this message, then sending -savePresentedItemChangesWithCompletionHandler:, and then, after you have invoked that completion handler, invoking your reacquirer.
      */
-    relinquishPresentedItemToReader$?(reader: NobjcObject | null): void;
+    relinquishPresentedItemToReader$?(reader: ((arg0: () => void) => void) | null): void;
     /**
      * Given that something in the system is waiting to write to the presented file or directory, do whatever it takes to ensure that the application will behave properly while that writing is happening, and then invoke the completion handler. The definition of "properly" depends on what kind of ownership model the application implements. Implementations of this method must always invoke the passed-in writer block because other parts of the system will wait until it is invoked or until the user loses patience and cancels the waiting. When an implementation of this method invokes the passed-in block it can pass that block yet another block, which will be invoked in the receiver's operation queue when writing is complete. A common sequence that your NSFilePresenter must handle is the file coordination mechanism sending this message, then sending -accommodatePresentedItemDeletionWithCompletionHandler: or -savePresentedItemChangesWithCompletionHandler:, and then, after you have invoked that completion handler, invoking your reacquirer. It is also common for your NSFilePresenter to be sent a combination of the -presented... messages listed below in between relinquishing and reacquiring.
      */
-    relinquishPresentedItemToWriter$?(writer: NobjcObject | null): void;
+    relinquishPresentedItemToWriter$?(writer: ((arg0: () => void) => void) | null): void;
     /**
      * Given that something in the system is waiting to read from the presented file or directory, do whatever it takes to ensure that the contents of the presented file or directory is completely up to date, and then invoke the completion handler. If successful (including when there is simply nothing to do) pass nil to the completion handler, or if not successful pass an NSError that encapsulates the reason why saving failed. Implementations of this method must always invoke the completion handler because other parts of the system will wait until it is invoked or the user loses patience and cancels the waiting. If this method is not implemented then the NSFilePresenter is assumed to be one that never lets the user make changes that need to be saved. For example, NSDocument has an implementation of this method that autosaves the document if it has been changed since the last time it was saved or autosaved. That way when another process tries to read the document file it always reads the same version of the document that the user is looking at in your application. (WYSIWGCBF - What You See Is What Gets Copied By Finder.) A shoebox application would also implement this method. The file coordination mechanism does not always send -relinquishPresentedItemToReader: or -relinquishPresentedItemToWriter: to your NSFilePresenter before sending this message. For example, other process' use of -[NSFileCoordinator prepareForReadingItemsAtURLs:options:writingItemsAtURLs:options:error:byAccessor:] can cause this to happen.
      */
-    savePresentedItemChangesWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
+    savePresentedItemChangesWithCompletionHandler$?(completionHandler: ((errorOrNil: _NSError) => void) | null): void;
     /**
      * Given that something in the system is waiting to delete the presented file or directory, do whatever it takes to ensure that the deleting will succeed and that the receiver's application will behave properly when the deleting has happened, and then invoke the completion handler. If successful (including when there is simply nothing to do) pass nil to the completion handler, or if not successful pass an NSError that encapsulates the reason why preparation failed. Implementations of this method must always invoke the completion handler because other parts of the system will wait until it is invoked or until the user loses patience and cancels the waiting. For example, NSDocument has an implementation of this method that closes the document. That way if the document is in the trash and the user empties the trash the document is simply closed before its file is deleted. This means that emptying the trash will not fail with an alert about the file being "in use" just because the document's file is memory mapped by the application. It also means that the document won't be left open with no document file underneath it. A shoebox application would only implement this method to be robust against surprising things like the user deleting its data directory while the application is running. The file coordination mechanism does not always send -relinquishPresentedItemToReader: or -relinquishPresentedItemToWriter: to your NSFilePresenter before sending this message. For example, other process' use of -[NSFileCoordinator prepareForReadingItemsAtURLs:options:writingItemsAtURLs:options:error:byAccessor:] can cause this to happen.
      */
-    accommodatePresentedItemDeletionWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
+    accommodatePresentedItemDeletionWithCompletionHandler$?(completionHandler: ((errorOrNil: _NSError) => void) | null): void;
     /**
      * Given that something in the system is waiting to evict the presented file or directory, do whatever it takes to ensure that the eviction will succeed and that the receiver's application will behave properly when the eviction has happened, and then invoke the completion handler. This must include calling `+[NSFileCoordinator removeFilePresenter:]`. If successful, pass nil to the completion handler. If not successful, or to prevent the eviction of the file, throw an error that encapsulates the reason. Implementations of this method must always invoke the completion handler because other parts of the system will wait until it is invoked or until the user loses patience and cancels the waiting. If this method is not implemented, eviction will fail.
      */
-    accommodatePresentedItemEvictionWithCompletionHandler$?(completionHandler: NobjcObject | null): void;
+    accommodatePresentedItemEvictionWithCompletionHandler$?(completionHandler: ((errorOrNil: _NSError) => void) | null): void;
     /**
      * Be notified that the file or directory has been moved or renamed, or a directory containing it has been moved or renamed. A typical implementation of this method will cause subsequent invocations of -presentedItemURL to return the new URL. The new URL may have a different file name extension than the current value of the presentedItemURL property. For example, NSDocument implements this method to handle document file moving and renaming. A shoebox application would only implement this method to be robust against surprising things like the user moving its data directory while the application is running. Not all programs use file coordination. Your NSFileProvider may be sent this message without being sent -relinquishPresentedItemToWriter: first. Make your application do the best it can in that case.
      */
@@ -45,7 +45,7 @@ export interface _NSFilePresenter {
     /**
      * Given that something in the system is waiting to delete a file or directory contained by the directory, do whatever it takes to ensure that the deleting will succeed and that the receiver's application will behave properly when the deleting has happened, and then invoke the completion handler. If successful (including when there is simply nothing to do) pass nil to the completion handler, or if not successful pass an NSError that encapsulates the reason why preparation failed. Implementations of this method must always invoke the completion handler because other parts of the system will wait until it is invoked or until the user loses patience and cancels the waiting. The file coordination mechanism does not always send -relinquishPresentedItemToReader: or -relinquishPresentedItemToWriter: to your NSFilePresenter before sending this message. For example, other process' use of -[NSFileCoordinator prepareForReadingItemsAtURLs:options:writingItemsAtURLs:options:error:byAccessor:] can cause this to happen.
      */
-    accommodatePresentedSubitemDeletionAtURL$completionHandler$?(url: _NSURL, completionHandler: NobjcObject | null): void;
+    accommodatePresentedSubitemDeletionAtURL$completionHandler$?(url: _NSURL, completionHandler: ((errorOrNil: _NSError) => void) | null): void;
     /**
      * Be notified that a file or directory contained by the directory has been added. If this method is not implemented but -presentedItemDidChange is, and the directory is actually a file package, then the file coordination machinery will invoke -presentedItemDidChange instead. Not all programs use file coordination. Your NSFileProvider may be sent this message without being sent -relinquishPresentedItemToWriter: first. Make your application do the best it can in that case.
      */

package/dist/Foundation/NSFileProviderService.d.ts

@@ -1,10 +1,11 @@
-import type { NobjcObject } from "objc-js";
+import type { _NSError } from "./NSError.js";
 import type { _NSObject } from "./NSObject.js";
+import type { _NSXPCConnection } from "./NSXPCConnection.js";
 import type { NSFileProviderServiceName } from "./NSFileProviderServiceName.js";
 export declare class _NSFileProviderService extends _NSObject {
     static alloc(): _NSFileProviderService;
     static new(): _NSFileProviderService;
     init(): _NSFileProviderService;
-    getFileProviderConnectionWithCompletionHandler$(completionHandler: NobjcObject | null): void;
+    getFileProviderConnectionWithCompletionHandler$(completionHandler: ((connection: _NSXPCConnection, error: _NSError) => void) | null): void;
     name(): NSFileProviderServiceName;
 }

package/dist/Foundation/NSFileVersion.d.ts

@@ -2,6 +2,7 @@ import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "./NSArray.js";
 import type { _NSCoding } from "./NSCoding.js";
 import type { _NSDate } from "./NSDate.js";
+import type { _NSError } from "./NSError.js";
 import type { _NSObject } from "./NSObject.js";
 import type { _NSPersonNameComponents } from "./NSPersonNameComponents.js";
 import type { _NSString } from "./NSString.js";
@@ -27,7 +28,7 @@ export declare class _NSFileVersion extends _NSObject {
     /**
      * Asynchronously return an array of NSFileVersions associated with the file located by the given URL, or nil if there is no such file or another error occurs. Versions returned by this method do not initially have their contents stored locally on the device, so a download may be required before you are able to access them. File attributes are accessible via -[NSURL getPromisedItemResourceValue:forKey:error:]. You can request a download by performing a coordinated read with NSFileCoordinator on the URL property of the resulting NSFileVersions. When a version is successfully downloaded, its contents are cached locally, and the version will no longer be returned by this method. The version will be returned by +[NSFileVersion otherVersionsOfItemAtURL:] instead, but will retain the same persistentIdentifier value. If the local version is later discarded, future invocations of this method may resume returning the version. If you need to get all versions for a document, both local and non-local, you should use an NSFilePresenter that implements -presentedItemDidGainVersion: and -presentedItemDidLoseVersion: and invoke +[NSFileCoordinator addFilePresenter:], +[NSFileVersion otherVersionsOfItemAtURL:], and this method within a single coordinated read.
      */
-    static getNonlocalVersionsOfItemAtURL$completionHandler$(url: _NSURL, completionHandler: NobjcObject | null): void;
+    static getNonlocalVersionsOfItemAtURL$completionHandler$(url: _NSURL, completionHandler: ((nonlocalFileVersions: _NSArray, error: _NSError) => void) | null): void;
     /**
      * For a file located by a URL, return the NSFileVersion identified by a persistent identifier of the sort returned by -persistentIdentifier, or nil if the version no longer exists.
      */

package/dist/Foundation/NSHTTPCookieStorage.d.ts

@@ -1,4 +1,3 @@
-import type { NobjcObject } from "objc-js";
 import type { _NSArray } from "./NSArray.js";
 import type { _NSDate } from "./NSDate.js";
 import type { _NSHTTPCookie } from "./NSHTTPCookie.js";
@@ -42,7 +41,7 @@ export declare class _NSHTTPCookieStorage extends _NSObject {
      */
     sortedCookiesUsingDescriptors$(sortOrder: _NSArray): _NSArray;
     storeCookies$forTask$(cookies: _NSArray, task: _NSURLSessionTask): void;
-    getCookiesForTask$completionHandler$(task: _NSURLSessionTask, completionHandler: NobjcObject | null): void;
+    getCookiesForTask$completionHandler$(task: _NSURLSessionTask, completionHandler: ((cookies: _NSArray) => void) | null): void;
     /** @abstract Get all the cookies @result An NSArray of NSHTTPCookies */
     cookies(): _NSArray | null;
     /** @abstract The cookie accept policy preference of the receiver. */

package/dist/Foundation/NSIndexSet.d.ts

@@ -29,21 +29,21 @@ export declare class _NSIndexSet extends _NSObject {
     containsIndexesInRange$(range: NSRange): boolean;
     containsIndexes$(indexSet: _NSIndexSet): boolean;
     intersectsIndexesInRange$(range: NSRange): boolean;
-    enumerateIndexesUsingBlock$(block: NobjcObject): void;
-    enumerateIndexesWithOptions$usingBlock$(opts: NSEnumerationOptions, block: NobjcObject): void;
-    enumerateIndexesInRange$options$usingBlock$(range: NSRange, opts: NSEnumerationOptions, block: NobjcObject): void;
-    indexPassingTest$(predicate: NobjcObject): number;
-    indexWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: NobjcObject): number;
-    indexInRange$options$passingTest$(range: NSRange, opts: NSEnumerationOptions, predicate: NobjcObject): number;
-    indexesPassingTest$(predicate: NobjcObject): _NSIndexSet;
-    indexesWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: NobjcObject): _NSIndexSet;
-    indexesInRange$options$passingTest$(range: NSRange, opts: NSEnumerationOptions, predicate: NobjcObject): _NSIndexSet;
+    enumerateIndexesUsingBlock$(block: (idx: number, stop: NobjcObject) => void): void;
+    enumerateIndexesWithOptions$usingBlock$(opts: NSEnumerationOptions, block: (idx: number, stop: NobjcObject) => void): void;
+    enumerateIndexesInRange$options$usingBlock$(range: NSRange, opts: NSEnumerationOptions, block: (idx: number, stop: NobjcObject) => void): void;
+    indexPassingTest$(predicate: (idx: number, stop: NobjcObject) => boolean): number;
+    indexWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: (idx: number, stop: NobjcObject) => boolean): number;
+    indexInRange$options$passingTest$(range: NSRange, opts: NSEnumerationOptions, predicate: (idx: number, stop: NobjcObject) => boolean): number;
+    indexesPassingTest$(predicate: (idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
+    indexesWithOptions$passingTest$(opts: NSEnumerationOptions, predicate: (idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
+    indexesInRange$options$passingTest$(range: NSRange, opts: NSEnumerationOptions, predicate: (idx: number, stop: NobjcObject) => boolean): _NSIndexSet;
     /**
      * The following three convenience methods allow you to enumerate the indexes in the receiver by ranges of contiguous indexes. The performance of these methods is not guaranteed to be any better than if they were implemented with enumerateIndexesInRange:options:usingBlock:. However, depending on the receiver's implementation, they may perform better than that. If the specified range for enumeration intersects a range of contiguous indexes in the receiver, then the block will be invoked with the intersection of those two ranges.
      */
-    enumerateRangesUsingBlock$(block: NobjcObject): void;
-    enumerateRangesWithOptions$usingBlock$(opts: NSEnumerationOptions, block: NobjcObject): void;
-    enumerateRangesInRange$options$usingBlock$(range: NSRange, opts: NSEnumerationOptions, block: NobjcObject): void;
+    enumerateRangesUsingBlock$(block: (range: NSRange, stop: NobjcObject) => void): void;
+    enumerateRangesWithOptions$usingBlock$(opts: NSEnumerationOptions, block: (range: NSRange, stop: NobjcObject) => void): void;
+    enumerateRangesInRange$options$usingBlock$(range: NSRange, opts: NSEnumerationOptions, block: (range: NSRange, stop: NobjcObject) => void): void;
     count(): number;
     /**
      * The following six methods will return NSNotFound if there is no index in the set satisfying the query.