
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@reactseals/renative-template-chat
Advanced tools
ReNative Template for Basic cross-platform chat application. iOS, Android, Web, MacOS Desktop
build universal cross-platform apps with react native
| Web | ||
|---|---|---|
![]() | ![]() | ![]() |
| Android | ||
![]() | ![]() | ![]() |
| macOS | ||
![]() | ![]() | ![]() |
0.31.3 or newer10.13.0 or newer6.4.1 or newer
Below you will find steps to enable Firebase on your chat app. These are platform specific steps, if you do not care about performance, you may only do the WEB & MacOS section and make data/Provider/instances/FirebaseProvider/index.web.js your main data provider, this will ignore React-Native-Firebase package, and iOS with Android will operate on the JS thread.
API_KEY=<your-api-key>
AUTH_DOMAIN=<your-auth-domain>'
DATABASE_URL=<your-database-url>
PROJECT_ID=<your-cloud-firestore-project>
STORAGE_BUCKET=<your-storage-bucket>
MESSAGING_SENDER_ID=<your-sender-id>
APP_ID=<your-app-id>
You may read this section if you feel confused how all platforms come together. These are the the things specific to ReNative and this template specifically.
All of the Authentication logic is kept in src/context/auth All of the data manipulation and managing logic is kept in src/data If you wish to change data provider from Firebase to some other, all you need to do is create your own provider implementation in src/data/Provider/instances.
Most of the components in this app are used by all of the supported platforms, you may read how it works in ReNative documentation. What you need to know here, is that main difference between the platforms is the navigation technology used. 1. For WEB we use the NextJS native navigation, so all the routes are in src/pages/ folder 2. For Mobile we use React-Navigation, we keep all the routes in src/MainNavigator.js 3. For MacOS we use the Reach Router, you can find the entry file in src/app.macos.js
Everything else should be understandable if you have any experience with React/React Native projects
| Web | ||
|---|---|---|
![]() | ![]() | ![]() |
| Feature | Version |
|---|---|
| Webpack | 3.11.0 |
| react-native-web | 0.9.1 |
| Babel Core | 7.1.2 |
rnv run -p web
RNV will run local server and attempt to open browser URL: http://0.0.0.0:8080/
If you only want to run server:
rnv start -p web
rnv build -p web
your deployable web app folder will be located in ./platformBuilds/<APP_ID>_web/public
Clean and Re-build platform project
rnv run -p web -r
Run with verbose logging:
rnv run -p web --info
Run app on custom port 9999:
rnv run -p web --port 9999
| Android | ||
|---|---|---|
![]() | ![]() | ![]() |
23.0.1 or newer for Android development| Feature | Version |
|---|---|
| Gradle | 4.10.1 |
| Android Gradle | 3.3.1 |
| Kotlin | 1.3.20 |
| Target SDK | 27 |
You can create variety of emulators via Android Studio IDE
|
|---|
NOTE: make sure you have 1 android device connected or 1 emulator running
rnv start
rnv run -p android
rnv start
rnv run -p android -d
This will run production version on your device (not connected to metro bundler)
You can configure each buldScheme ie -s release in your config file ./appConfigs/<YOUR_APP_CONFIG>/config.json
rnv start
rnv run -p android -s release -d
Clean and Re-build platform project
rnv run -p android -r
Launch specific android emulator:
rnv target launch -p android -t Nexus_5X_API_26
Launch app with specific iOS simulator (let ReNative to give you the list of available options):
rnv run -p android -t ?
Launch specific emulator :
rnv target launch -p android -t Nexus_5X_API_26
Launch specific emulator (let ReNative to give you the list of available options):
rnv target launch -p android -t ?
Get list of all available devices
rnv target list -p android
Get device/simulator logs
rnv log -p android
Get device/simulator logs with filter
rnv log -p android -f com.myapp
| macOS | ||
|---|---|---|
![]() | ![]() | ![]() |
| Feature | Version |
|---|---|
| electron | 2.0.0 |
| react-native-web | 0.9.9 |
| electron-builder | 20.28.2 |
rnv run -p macos
This will run production version on your simulator (not connected to devserver)
You can configure each buldScheme ie -s release in your config file ./appConfigs/<YOUR_APP_CONFIG>/config.json
rnv run -p macos -s release
FAQs
ReNative Template for Basic cross-platform chat application. iOS, Android, Web, MacOS Desktop
We found that @reactseals/renative-template-chat demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.