Veeck
Veeck
We encountered this bug also when upgrading vom v7 to v8 in our monorepo. Afterwards our seperate app failed the production build when using our monorepo libraries...
We "fixed" it by updating sb to v8 manually and not by using the nx migration process I was told. Plus we deactivated pnpm caching in our nx/github ci setup...
I am not sure if @obipawan still is interested in maintaining this repo (or has the time), although we and lots others find it helpful. So first: thanks to them...
We at Volksverpetzer would be happy to maintain this, the repo is already forked and available at https://github.com/Volksverpetzer/react-native-hyperlink Big question to start with though: What name should the new fork...
> Generally, the convention is to prefix the package name with the author/company name. > > So `@volksverpetzer/react-native-hyperlink` is a good solution. I just published v0.0.23 under https://www.npmjs.com/package/@volksverpetzer/react-native-hyperlink
I'd go for the stringify
ok, then lets remove it
Thanks for the clarification. Converted this to a draft until I find time to translate the new texts. Hopefully this evening
ready to be merged @tdewey-rpi
Could this get merged before the next rc, so I can check if the translations fit on the screen @tdewey-rpi ?