-
Notifications
You must be signed in to change notification settings - Fork 6
feat: update packages to latest Nitro version #64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Updated React Native from 0.76.0 to 0.80.1 - Updated React from 18.3.1 to 19.1.0 (required by RN 0.80) - Updated React Native Nitro Modules from 0.20.0 to 0.26.3 - Updated Nitro Codegen from 0.20.0 to 0.26.3 - Updated TypeScript from 5.1.3 to 5.8.3 - Updated ESLint and related packages to latest in major version - Updated @types/jest from 29.x to 30.x - Updated prettier, vitest, and other dev dependencies Breaking changes addressed: - Fixed TypeScript compilation errors for React 19 compatibility - Added type annotations and @ts-ignore for stream/event compatibility - Updated W3C API implementations for new React types Generated code updated with latest Nitro 0.26.3: - Regenerated all hybrid object specifications - Updated autolinking configurations - Updated Swift, Kotlin, and C++ bindings
Co-authored-by: grabbou <[email protected]>
|
…s implementations - Removed all @ts-ignore statements from WebSocket dispatchEvent calls - Restored EventTarget interface implementation with proper generics in WebSocket - Restored globalThis.File interface implementation in File class - Restored globalThis.CompressionStream interface in CompressionStream class - Added type assertions instead of 'any' types for polyfill/native type bridging Note: TypeScript 5.8.3 reveals fundamental type incompatibilities between web-streams-polyfill and native DOM types that were not caught by TS 5.1.3. These need to be resolved either by: 1. Updating to compatible stream polyfill versions 2. Creating proper type declaration merging 3. Using conditional types for polyfill/native environments The code maintains strict typing contracts while using type assertions where polyfill and native types are functionally equivalent but structurally incompatible at the type level.
… audit Co-authored-by: grabbou <[email protected]>
|
hey @grabbou 👋 do you have an ETA of this merge? 🙏 Or maybe release a canary version? |
Updates to latest Nitro Modules before continuing further work.