Unable to resolve types with v0.35.0

<!-- If this issue relates to installation, please use https://github.com/lovell/sharp/issues/new?labels=installation&template=installation.md instead. --> ## Possible bug ### Is this a possible bug in a feature of sharp, unrelated to installation? <!-- Please place an [x] in the box to confirm. --> - [x] Running `npm install sharp` completes without error. - [x] Running `node -e "import 'sharp'"` completes without error. If you cannot confirm both of these, please open an [installation issue](https://github.com/lovell/sharp/issues/new?labels=installation&template=installation.md) instead. ### Are you using the latest version of sharp? <!-- Please place an [x] in the box to confirm. --> - [x] I am using the latest version of `sharp` as reported by `npm view sharp dist-tags.latest`. If you cannot confirm this, please upgrade to the latest version and try again before opening an issue. If you are using another package which depends on a version of `sharp` that is not the latest, please open an issue against that package instead. ### What is the output of running `npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp`? ``` System: OS: macOS 26.5 CPU: (10) arm64 Apple M1 Max Memory: 3.26 GB / 64.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 24.14.1 - ~/.nvm/versions/node/v24.14.1/bin/node npm: 11.16.0 - ~/.nvm/versions/node/v24.14.1/bin/npm Deno: 2.7.14 - /opt/homebrew/bin/deno npmPackages: sharp: 0.35.0 => 0.35.0 ``` ### Does this problem relate to file caching? The default behaviour of libvips is to cache input files, which can lead to `EBUSY` or `EPERM` errors on Windows. Use [`sharp.cache(false)`](https://sharp.pixelplumbing.com/api-utility#cache) to switch this feature off. - [x] Adding `sharp.cache(false)` does not fix this problem. ### Does this problem relate to images appearing to have been rotated by 90 degrees? Images that contain EXIF Orientation metadata are not auto-oriented. By default, EXIF metadata is removed. - To auto-orient pixel values use the parameter-less [`rotate()`](https://sharp.pixelplumbing.com/api-operation#rotate) operation. - To retain EXIF Orientation use [`keepExif()`](https://sharp.pixelplumbing.com/api-output#keepexif). - [x] Using `rotate()` or `keepExif()` does not fix this problem. ### What are the steps to reproduce? 1. Run `npm lint` or open a project using sharp in an IDE with typescript support, which worked with v0.34.5. 2. It will show errors like: ``` Could not find a declaration file for module sharp. /<DIR>/node_modules/sharp/dist/index.mjs implicitly has an any type. There are types at /<DIR>/node_modules/sharp/lib/index.d.ts, but this result could not be resolved when respecting package.json “exports”. The sharp library may need to update its package.json or typings. (ts 7016) ``` ``` error Unsafe call of a type that could not be resolved @typescript-eslint/no-unsafe-call ``` ### What is the expected behaviour? Lint runs through fine, no issues in IDE, type resolving works normally. ### Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem I tried setting up a codepen but it didn't work, I don't have more time to spend on this, sorry. ### Please provide sample image(s) that help explain this problem This is not related to images.