Comparing version
{ | ||
"name": "rner", | ||
"version": "0.0.4", | ||
"version": "0.0.5", | ||
"main": "./lib/rner.js", | ||
@@ -10,3 +10,3 @@ "license": "Apache-2.0", | ||
"README.md", | ||
"index.ts" | ||
"index.js" | ||
], | ||
@@ -24,3 +24,3 @@ "repository": { | ||
"bin": { | ||
"rner": "index.ts" | ||
"rner": "index.js" | ||
}, | ||
@@ -27,0 +27,0 @@ "dependencies": { |
# RNer (React Native App Maker) | ||
### This is a sub-framework of React-Naitve, and it provides a way to create screens and components for the mobile application. | ||
This is a sub-framework of React-Naitve, and it provides a way to create screens and components for the mobile application. | ||
@@ -16,4 +16,10 @@ ## Installation | ||
### Creating a project | ||
ex: App name is Demo | ||
``` | ||
rner new Demo | ||
``` | ||
### Philosophy | ||
@@ -20,0 +26,0 @@ In terms of structural views of React-Native app, there are many ways to create a screen or component in React-Native development. |
Trivial Package
Supply chain riskPackages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.
Found 1 instance in 1 package
3046
57.5%7
133.33%57
1040%39
18.18%0
-100%