I'm sorry to post this here but didn't know where else to put it. I've recently migrated our project (as advised) from react-native-heap to @heap/heap-react-native-bridge. However, the NPM register seems to link to a non-existing GitHub repo (https://github.com/heap/heap-react-native-core).
This makes it hard for us to use the dependency; it breaks some of our automated tooling and makes it impossible to see changes or even changelogs with newer versions becoming available. We have to go through the included code manually to see what changed.
Could it be that the repository is unintentionally set to private? Could this be updated to help us use the new core based libraries?
Hi heap team,
I'm sorry to post this here but didn't know where else to put it. I've recently migrated our project (as advised) from
react-native-heapto@heap/heap-react-native-bridge. However, the NPM register seems to link to a non-existing GitHub repo (https://github.com/heap/heap-react-native-core).This makes it hard for us to use the dependency; it breaks some of our automated tooling and makes it impossible to see changes or even changelogs with newer versions becoming available. We have to go through the included code manually to see what changed.
Could it be that the repository is unintentionally set to private? Could this be updated to help us use the new core based libraries?
Thanks in advance! 🙏
Rik