Convert LazyFile/LazyBlob to standalone classes
#10913
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes subclassing from
LazyFile/LazyBlobto fix compatibility issues with Bun's native optimizations and updates all consumers to use the new APIs.@remix-run/lazy-fileno longer extends nativeFile/Blob. Instead,LazyFileandLazyBlobimplement the same interface as standalone classes. Users must now call.stream()forResponsebodies or.toFile()/.toBlob()for APIs requiring native types (e.g.FormData).@remix-run/fshas renamedopenFile()toopenLazyFile()and removed thegetFile()alias to explicitly reflect that it returns aLazyFile, not a nativeFile.@remix-run/responsenow accepts any file-like object via a genericFileLikeinterface, supporting both nativeFileandLazyFile.@remix-run/file-storageand@remix-run/static-middlewarehave been updated to use the newopenLazyFile()API.