Just wanna say that the tooling switch to bun, oxlint, and whatever I have not noticed yet... sucks big time!
I'm telling it from the perspective of knowing that you don't usually bother to respond to any issues opened in the library, and thus most of the real issues opened again and again are just closed automatically by the GitHub bot after some time (e.g. #3014, #3289, #3317 I cared about)... neither do you merge in 3rd party PRs, also letting them to auto-close after a time (e.g. #3575, #3290, #3318)... to the degree that the only way for me and some other folks to get react-native-webview working for us was to fork it (https://www.npmjs.com/package/@dr.pogodin/react-native-webview).
Unnecessary tooling changes from the tools used by RN itself to other stuff is quite annoying as it just complicates maintaining of such forks, without any obvious benefits (unlike if the same time was spent into addressing existing library issues, at least those for which PRs were opened by other ppl).
Just wanna say that the tooling switch to bun, oxlint, and whatever I have not noticed yet... sucks big time!
I'm telling it from the perspective of knowing that you don't usually bother to respond to any issues opened in the library, and thus most of the real issues opened again and again are just closed automatically by the GitHub bot after some time (e.g. #3014, #3289, #3317 I cared about)... neither do you merge in 3rd party PRs, also letting them to auto-close after a time (e.g. #3575, #3290, #3318)... to the degree that the only way for me and some other folks to get
react-native-webviewworking for us was to fork it (https://www.npmjs.com/package/@dr.pogodin/react-native-webview).Unnecessary tooling changes from the tools used by RN itself to other stuff is quite annoying as it just complicates maintaining of such forks, without any obvious benefits (unlike if the same time was spent into addressing existing library issues, at least those for which PRs were opened by other ppl).