Add New Architecture support for react-native-stallion

[general-maximus-decimus]

📝 Why & how

Why: The react-native-stallion entry needed to surface its companion Expo config plugin and Expo Go compatibility so users discovering it through the directory know it works in Expo-managed projects without ejecting. stallion-cli is the developer tooling that pairs with react-native-stallion — it handles bundle uploads, release management, and OTA workflows. Adding it to the directory makes the full Stallion toolchain discoverable in one place

How: Updated the existing react-native-stallion entry in react-native-libraries.json:

• Added configPlugin set to the expo-stallion-plugin GitHub URL (https://github.com/stallion-tech/expo-stallion-plugin)
• Added expoGo: true to indicate Expo Go support
• newArchitecture: true: Compatible with React Native's New Architecture (Fabric/TurboModules)
• Appended a new entry at the end of
  react-native-libraries.json:
• githubUrl:
  https://github.com/stallion-tech/stallion-cli
• npmPkg: stallion-cli for npm install
  resolution

✅ Checklist

• Added library to react-native-libraries.json
• Updated library in react-native-libraries.json

• Documented how you found or replicated the issue.
• Explained how you fixed the issue or built the feature.
• Described how to use or verify the change.

[Simek]

Hey @general-maximus-decimus, thanks for adding a new entry! 👍

New entries should be placed at the end of file, since we use that order for "Recently added" sort.

You can also add a config plugin URL directly to the package entry, see:

• https://github.com/react-native-community/directory#configplugin

[general-maximus-decimus]

Hey @Simek , would it be appropriate to also add our stallion-cli repo to react-native-libraries.json? It's the CLI companion to react-native-stallion (used for managing OTA releases, uploading bundles, etc.).

[Simek]

@general-maximus-decimus you can add for discoverability it if you want.

Since you recommends global installation some compatibility features like checks in expo/expo-doctor checks won't work (package would not be detected), but not a problem on our side.

Just please tag the entry with "dev": true flag, like https://reactnative.directory/package/ignite-cli does.

[Simek]

Thanks for the updates @general-maximus-decimus!

Since you have disabled the permission for maintainers to edit the PR, I cannot resolve the conflict. When you update the branch it should be ready to ship. 🙂

[general-maximus-decimus]

Hey @Simek , Thanks for the update. I’ve resolved the merge conflicts and updated the branch. It should now be ready to ship.