react-native-electron | Electron extensions to React Native for Web | Frontend Framework library

by PaulLeCam TypeScript Version: 0.18.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | react-native-electron Summary

react-native-electron is a TypeScript library typically used in User Interface, Frontend Framework, React Native, React, Electron applications. react-native-electron has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This project aims to provide extensions to React Native for Web targeted to the Electron environment to support additional modules exposed by React Native (Alert) or alternative implementations (Linking) using Electron APIs.

Support

Quality

Security

License

Reuse

Support

react-native-electron has a low active ecosystem.

It has 218 star(s) with 24 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 7 have been closed. On average issues are closed in 52 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of react-native-electron is 0.18.0

Quality

react-native-electron has 0 bugs and 0 code smells.

Security

react-native-electron has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

react-native-electron code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

react-native-electron is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

react-native-electron releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed react-native-electron and discovered the below as its top functions. This is intended to give you an instant insight into react-native-electron implemented functionality, and help decide if they suit your requirements.

Creates a uri bar .
Creates a new navBar .
Select a uri bar
Returns the new website .
Compiles a style name

Get all kandi verified functions for this library.

react-native-electron Key Features

No Key Features are available at this moment for react-native-electron.

react-native-electron Examples and Code Snippets

No Code Snippets are available at this moment for react-native-electron.

Community Discussions

Trending Discussions on react-native-electron

electron-builder install-app-deps tries to include react-native while I have an alias set in webpack to react-native-electron

QUESTION

electron-builder install-app-deps tries to include react-native while I have an alias set in webpack to react-native-electron

Asked 2018-Jun-06 at 15:29

How do I tell electron-builder to package react-native-electron instead of react-native? I could not find anything about alias in the electron-builder docs and it's also surprising because it's not a native module so it doesn't contain any .node files, and webpack (through electon-webpack) has taken care of all the packaging.

This is on Ubuntu.

The development build using the webpack server managed by electron-webpack (with the command electron-webpack dev) works perfectly.

If I try yarn add react-native it does build but when I start the resulting app it opens but does nothing.

I also tried to copy the react-native-electron folder and renaming it to react-native. Then it does build but if I start it, it does not even open but I do see it doing nothing in system monitor.

When I try electron-builder install-app-deps without react-native it errors out with:

...

ANSWER

Answered 2018-Jun-06 at 15:29

Seems like the definition of devDependencies is a bit different than I'm used to. In this case, packages that would normally just be dependencies are now only used by webpack and not by electron-builder. electron-builder includes the dependencies but not the devDependencies. So all js modules with no native component can be in devDependencies because they don't have to be included in the final electron build because webpack has already bundled them. electron-builder does not look at the webpack config so it does not know about the alias, but as it turns out packages like ract-navigation and their subdependencies (like react-native) should not be in the build twice anyway.

So move everything that should not be included separately to devDependencies and the app will compile. It did not start because of errors but that's another problem probably

Source https://stackoverflow.com/questions/50620640

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install react-native-electron

electron, react and react-native-web are required peer dependencies, make sure to install them as well:. react-art is also needed if you use ART.
In order for the APIs exposed by react-native-electron to be accessible in Electron's render process, the following setup must be applied:.
The react-native-electron/main module must be imported in the main process
BrowserWindow instances must be created with the preload script from react-native-electron/preload, for example:

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: