infinitered Github contribution chart
infinitered Github Stats
infinitered Most Used Languages

Activity

04 Oct 2022

Colkas

started

Started On 04 Oct 2022 at 07:47:40
Issue Comment

Sergioisidoro

Yarn unable to launch expo:web, missing package "webpack-dev-server"

Describe the bug

  1. npx ignite-cli new IgniteExpoWebTest --bundle=com.igniteexpowebtest --git --install-deps --overwrite=false --packager=yarn --target-path=/Users/fcalise/code/IgniteExpoWebTest --remove-demo=false
  2. cd IgniteExpoWebTest
  3. yarn expo:web

Observe the following in the terminal (can ignore the bit about the port in use):

yarn expo:web
yarn run v1.22.19
$ expo start --web
Starting project at /Users/fcalise/code/IgniteExpoWebTest
› Port 19000 is running chain-react-app-2023 in another window
  /Users/fcalise/code/ChainReactApp2023 (pid 21462)
✔ Use port 19001 instead? … yes
Some dependencies are incompatible with the installed expo version:
  react-native@0.69.5 - expected version: 0.69.6
  react-native-safe-area-context@4.3.4 - expected version: 4.3.1
Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install react-native@0.69.6 react-native-safe-area-context@4.3.1
Starting Metro Bundler
CommandError: Missing package "webpack-dev-server" in the project. Try running the command again. (cwd: /Users/fcalise/code/IgniteExpoWebTest)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 

If you use the npm package manager, the project is able to start up via npm run expo:web

Ignite version

8.0.1

Additional info

System
  platform           darwin
  arch               arm64
  cpu                10 cores            Apple M1 Pro
  directory          IgniteExpoWebTest   /Users/fcalise/code/IgniteExpoWebTest

JavaScript (and globally-installed packages)
  node                16.14.2      /Users/fcalise/.nvm/versions/node/v16.14.2/bin/node
  npm                 8.5.0        /Users/fcalise/.nvm/versions/node/v16.14.2/bin/npm
    corepack          0.10.0
    eas-cli           2.1.0
    expo-cli          6.0.2
    gatsby-cli        4.21.0
    ignite-cli        8.0.1
    npm               8.5.0
    yarn              1.22.19
  yarn                1.22.19      /Users/fcalise/.nvm/versions/node/v16.14.2/bin/yarn
    create-expo-app   1.1.2
  pnpm                -            not installed
  expo                46.0.14      managed

Ignite
  ignite-cli         8.0.1        /Users/fcalise/.nvm/versions/node/v16.14.2/bin/ignite
  ignite src         src          /Users/fcalise/code/ignite/src

Android
  java               11.0.14.1    /Users/fcalise/.asdf/shims/java
  android home       -            /Users/fcalise/Library/Android/sdk

iOS
  xcode              14.0
  cocoapods          1.11.3       /opt/homebrew/bin/pod

Tools
  git                git version 2.37.0 (Apple Git-136)   /usr/bin/git 

Forked On 04 Oct 2022 at 07:25:08

Sergioisidoro

How are you doing now after yarn add -D webpack-dev-server@^3 ?

After running the generator with :latest instead of :edge which fixed the asset issue, everything now works 👌

But the coincidence of a resource missing and a webpack issue made me immediately point fingers to webpack 😅 Thanks for the help :)

Commented On 04 Oct 2022 at 07:25:08

Joshuayoes

Fix demo screen and screen generator typings

Please verify the following:

  • [x] yarn test jest tests pass with new tests, if relevant

Describe your PR

  • Closes #2253, Added support for generators for win32 platform
  • Closes #2247, Newly generated screen would result in:
import React, { FC } from "react"
import { observer } from "mobx-react-lite"
import { ViewStyle } from "react-native"
import { StackScreenProps } from "@react-navigation/stack"
import { AppStackScreenProps } from "../navigators"
import { Screen, Text } from "../components"
// import { useNavigation } from "@react-navigation/native"
// import { useStores } from "../models"

// STOP! READ ME FIRST!
// To fix the TS error below, you'll need to add the following things in your navigation config:
// - Add `Test: undefined` to AppStackParamList
// - Import your screen, and add it to the stack:
//     `<Stack.Screen name="Test" component={TestScreen} />`
// Hint: Look for the 🔥!

// REMOVE ME! ⬇️ This TS ignore will not be necessary after you've added the correct navigator param type
// @ts-ignore
export const TestScreen: FC<StackScreenProps<AppStackScreenProps, "Test">> = observer(
  function TestScreen() {
    // Pull in one of our MST stores
    // const { someStore, anotherStore } = useStores()

    // Pull in navigation via hook
    // const navigation = useNavigation()
    return (
      <Screen style={$root} preset="scroll">
        <Text text="test" />
      </Screen>
    )
  },
)

const $root: ViewStyle = {
  flex: 1,
} 

Merged On 04 Oct 2022 at 07:20:02

Joshuayoes

Looks good to me! Good work on this

Commented On 04 Oct 2022 at 07:20:02
Issue Comment

Frankcalise

Yarn unable to launch expo:web, missing package "webpack-dev-server"

Describe the bug

  1. npx ignite-cli new IgniteExpoWebTest --bundle=com.igniteexpowebtest --git --install-deps --overwrite=false --packager=yarn --target-path=/Users/fcalise/code/IgniteExpoWebTest --remove-demo=false
  2. cd IgniteExpoWebTest
  3. yarn expo:web

Observe the following in the terminal (can ignore the bit about the port in use):

yarn expo:web
yarn run v1.22.19
$ expo start --web
Starting project at /Users/fcalise/code/IgniteExpoWebTest
› Port 19000 is running chain-react-app-2023 in another window
  /Users/fcalise/code/ChainReactApp2023 (pid 21462)
✔ Use port 19001 instead? … yes
Some dependencies are incompatible with the installed expo version:
  react-native@0.69.5 - expected version: 0.69.6
  react-native-safe-area-context@4.3.4 - expected version: 4.3.1
Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install react-native@0.69.6 react-native-safe-area-context@4.3.1
Starting Metro Bundler
CommandError: Missing package "webpack-dev-server" in the project. Try running the command again. (cwd: /Users/fcalise/code/IgniteExpoWebTest)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 

If you use the npm package manager, the project is able to start up via npm run expo:web

Ignite version

8.0.1

Additional info

System
  platform           darwin
  arch               arm64
  cpu                10 cores            Apple M1 Pro
  directory          IgniteExpoWebTest   /Users/fcalise/code/IgniteExpoWebTest

JavaScript (and globally-installed packages)
  node                16.14.2      /Users/fcalise/.nvm/versions/node/v16.14.2/bin/node
  npm                 8.5.0        /Users/fcalise/.nvm/versions/node/v16.14.2/bin/npm
    corepack          0.10.0
    eas-cli           2.1.0
    expo-cli          6.0.2
    gatsby-cli        4.21.0
    ignite-cli        8.0.1
    npm               8.5.0
    yarn              1.22.19
  yarn                1.22.19      /Users/fcalise/.nvm/versions/node/v16.14.2/bin/yarn
    create-expo-app   1.1.2
  pnpm                -            not installed
  expo                46.0.14      managed

Ignite
  ignite-cli         8.0.1        /Users/fcalise/.nvm/versions/node/v16.14.2/bin/ignite
  ignite src         src          /Users/fcalise/code/ignite/src

Android
  java               11.0.14.1    /Users/fcalise/.asdf/shims/java
  android home       -            /Users/fcalise/Library/Android/sdk

iOS
  xcode              14.0
  cocoapods          1.11.3       /opt/homebrew/bin/pod

Tools
  git                git version 2.37.0 (Apple Git-136)   /usr/bin/git 

Forked On 04 Oct 2022 at 07:12:30

Frankcalise

@sergioisidoro yeah sorry that asset thing was what commenced the looking into Expo web, which then lead to finding out about the issue with yarn!

How are you doing now after yarn add -D webpack-dev-server@^3 ?

Console isn't completely clean yet (we'll get there) but seems to be building and running now for me.

Commented On 04 Oct 2022 at 07:12:30

Frankcalise

chore(docs): update ignite-cli@next to ignite-cli@latest (#2244)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

docs(components): Add documentation for new Maverick Toggle Component (#2229)

  • docs(components): Add documentation for new Maverick Toggle Component

  • docs(Components-Toggle.md): spelling

  • docs(Components-Toggle.md): add note about status=disabled

Co-authored-by: Joshua Yoes joshua.r.yoes@gmail.com

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

fix: error on running ignite-cli doctor (#2248)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

chore(release): 8.2.1 [skip ci]

8.2.1 (2022-10-04)

Bug Fixes

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

fix: Remove SafeAreaView in favor of useSafeAreaInsets hook (#2238)

  • Remove SafeAreaView in favor of useSafeAreaInsets hook

  • Update to suggested cleaner syntax

Co-authored-by: Jamon Holmgren jamonholmgren@gmail.com

Co-authored-by: Jamon Holmgren jamonholmgren@gmail.com

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

chore(release): 8.2.2 [skip ci]

8.2.2 (2022-10-04)

Bug Fixes

  • Remove SafeAreaView in favor of useSafeAreaInsets hook (#2238) (813c34e)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

Add Logout button to Debug screen (#2246)

  • fix(boilerplate): moved DebugScreen last in tab order

  • feat(boilerplate): added Logout to DemoDebugScreen

  • fix(boilerplate): added logout to DemoDebugScreen

  • fix(boilerplate): clear out authEmail/Password on logout

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

fix: update styles array in component generator template (#2251)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

chore(release): 8.2.3 [skip ci]

8.2.3 (2022-10-04)

Bug Fixes

  • update styles array in component generator template (#2251) (b61047b)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

fix(package.json): pin "react-error-overlay": "6.0.9"

Co-authored-by: Ahmed Bodiwala ahmed_bodi@msn.com See issue for more context: https://github.com/infinitered/ignite/issues/2233

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

chore(release): 8.2.4 [skip ci]

8.2.4 (2022-10-04)

Bug Fixes

  • package.json: pin "react-error-overlay": "6.0.9" (876d033)

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

Merge branch 'master' into fix-2274/demo-typings

Pushed On 04 Oct 2022 at 07:04:35

Frankcalise

fix(generators): updated newline check for win32

Pushed On 04 Oct 2022 at 06:56:04

Frankcalise

fix(boilerplate): removed unused import from Screen generator

Pushed On 04 Oct 2022 at 06:46:28
Issue Comment

Frankcalise

ignite app size is 30.2 mb

why app size is so big 30.2 mb without any huge libraries ?

Forked On 04 Oct 2022 at 06:36:28

Frankcalise

This app bundle size topic has been discussed over at issues https://github.com/infinitered/ignite/issues/2240 and https://github.com/infinitered/ignite/issues/1947#issuecomment-1223985929 so I'm going to close this for now.

Closing this for now but feel free to bring it back up in Discussions or Community Slack

Commented On 04 Oct 2022 at 06:36:28
Issue Comment

Joshuayoes

When using Hermes in release build variants, Android crashes with java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so

Describe the bug

As the title says, I'm using a build variant called development, which uses our release signing config and generally replicates a release build.

When I build the app locally in debug mode, it works fine. When I build the development build the app crashes immediately, and in Android Studio I see:

--------- beginning of crash E/AndroidRuntime: FATAL EXCEPTION: main Process: com.appname.development, PID: 4513 java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so SoSource 0: com.facebook.soloader.DirectorySoSource[root = /data/app/~~yknNsxEbOR9vWgYxlcKx6g==/com.appname.development-uGOd6eC09Qm6p_dL_1XTtQ==/lib/arm64 flags = 0] SoSource 1: com.facebook.soloader.DirectApkSoSource[root = /data/app/~~yknNsxEbOR9vWgYxlcKx6g==/com.appname.development-uGOd6eC09Qm6p_dL_1XTtQ==/base.apk!/lib/arm64-v8a] SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2] SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2] Native lib dir: /data/app/~~yknNsxEbOR9vWgYxlcKx6g==/com.appname.development-uGOd6eC09Qm6p_dL_1XTtQ==/lib/arm64 result: 0 at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:1098) at com.facebook.soloader.SoLoader.loadLibraryBySoNameImpl(SoLoader.java:914) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:826) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:773) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:743) at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(JSCExecutor.java:24) at com.facebook.react.jscexecutor.JSCExecutor.(JSCExecutor.java:20) at com.facebook.react.jscexecutor.JSCExecutor.loadLibrary(Unknown Source:0) at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:351) at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:318) at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:95) at expo.modules.ReactNativeHostWrapperBase.createReactInstanceManager(ReactNativeHostWrapperBase.kt:33) at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:42) at com.appname.MainApplication.onCreate(MainApplication.java:66) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1211) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6725) at android.app.ActivityThread.access$1500(ActivityThread.java:247) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2053) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7839) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

Ignite version

7.15.0

Additional info

This ONLY happens when using Hermes, and only happened after I upgraded to RN 0.68.2 (from 0.66.3 I think, where it worked fine).

Relevant parts of build.gradle:

 // React native config setup
project.ext.envConfigFiles = [
    debug: ".env.development",
    development: ".env.development",
    qa: ".env.qa",
    release: ".env.production",
]

// later...

 buildTypes {
        debug {
            signingConfig signingConfigs.debug
            applicationIdSuffix ".development"
        }
    
        development {
            signingConfig signingConfigs.debug
            applicationIdSuffix ".development"
            matchingFallbacks = ['release']
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
        
        qa {
            signingConfig signingConfigs.release
            applicationIdSuffix ".qa"
            matchingFallbacks = ['release']
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
        
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://reactnative.dev/docs/signed-apk-android.
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }

    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // https://developer.android.com/studio/build/configure-apk-splits.html
            // https://developer.android.com/studio/build/configure-apk-splits.html
            def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        defaultConfig.versionCode * 1000 + versionCodes.get(abi)

            }
        }
    } 

Forked On 04 Oct 2022 at 06:12:40

Joshuayoes

Since this isn't entirely related to Ignite, and our default workflow out of the box, I'm going to close this issue for now.

However, in the future, we are working on a project called Ignite Cookbook, where we document common patterns in articles. I think multiple builds would be a good candidate for this. So I'm going to close the issue for now, but add the cookbook tag.

Commented On 04 Oct 2022 at 06:12:40
Issue Comment

Joshuayoes

Boilerplate Android build fails on Appcenter with "Could not read script '/' as it is a directory."

What's going on?

When using the default boilerplate, building locally works fine but an Appcenter (and potentially other cloud build tools, not sure), you get this error:

Starting a Gradle Daemon (subsequent builds will be faster)
Gradle 7.3.3

FAILURE: Build failed with an exception.

* Where:
Settings file '/Users/runner/work/1/s/ThriveBusiness/android/settings.gradle' line: 4

* What went wrong:
A problem occurred evaluating settings 'Thriday'.
> Could not read script '/' as it is a directory.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 21s
Error: /Users/runner/work/1/s/ThriveBusiness/android/gradlew failed with return code: 1
    at ChildProcess.<anonymous> (/Users/runner/work/_tasks/Gradle_8d8eebd8-2b94-4c97-85af-839254cc6da4/1.128.0/node_modules/vsts-task-lib/toolrunner.js:569:30)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:920:16)
    at Socket.<anonymous> (internal/child_process.js:351:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:509:12)
##[error]Error: /Users/runner/work/1/s/ThriveBusiness/android/gradlew failed with return code: 1 

This is caused by lines like this:

apply from: new File(["node", "--print", "require.resolve('expo/package.json')"].execute().text.trim(), "../scripts/autolinking.gradle"); 

The suggested method from Expo is to do use .execute(null, rootDir).text.trim() instead, like this:

apply from: new File(["node", "--print", "require.resolve('expo/package.json')"].execute(null, rootDir).text.trim(), "../scripts/autolinking.gradle") 

A similar change has to be made on /app/build.gradle at this line:

apply from: new File(["node", "--print", "require.resolve('react-native/package.json')"].execute().text.trim(), "../react.gradle"); 

It fails, but if you change it to .execute(null, rootDir).text.trim() then it works.

Forked On 04 Oct 2022 at 06:10:22

Joshuayoes

@jvgeee could you submit a PR with the gradle change that fixed it for you?

Commented On 04 Oct 2022 at 06:10:22
Issue Comment

Joshuayoes

New app gets created but does not start (windows + android)

What's going on? When I start a new app using the template, it creates the app successfully but when I run pnpm run android it gives the error in the screenshot. I even tried deleting the node modules and doing a normal npm install but that too gives a similar error. My android env is fine as other react-native apps work fine. err2


Steps to reproduce

  1. npx ignite-cli new PizzaApp
  2. cd PizzaApp
  3. pnpm run android

npx ignite-cli doctor results: doc

Forked On 04 Oct 2022 at 06:09:19

Joshuayoes

There has been a lot of changes since this issue last had activity. We have release a new major version of Ignite, codenamed Maverick. This is going to be closed for now, but please re-open if this still needs attention.

Commented On 04 Oct 2022 at 06:09:19
Issue Comment

Joshuayoes

Performance stack navigation when use enableScreens()

Performance stack navigation when use enableScreens()

By default enableScreens() turn on, the animation when I navigate to other screen it will make app slow than I turn off enableScreens(false).

Forked On 04 Oct 2022 at 06:06:49

Joshuayoes

There has been a lot of changes since this issue last had activity. We have release a new major version of Ignite, codenamed Maverick. This is going to be closed for now, but please re-open if this still needs attention.

Commented On 04 Oct 2022 at 06:06:49
Issue Comment

Joshuayoes

Cannot find module ...node_modules/react-native/cli.js'

I was init project via ignite then i build it. i have problem someone help me fix it. please

My package.json:

{
  "name": "verify-app",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "react-native start",
    "ios": "react-native run-ios",
    "android": "react-native run-android",
    "test:e2e": "detox test -c ios.sim.debug",
    "build:e2e": "detox build -c ios.sim.debug",
    "ci:test:e2e": "detox test -c ios.sim.release -l verbose --cleanup",
    "ci:build:e2e": "detox build -c ios.sim.release",
    "compile": "tsc --noEmit -p . --pretty",
    "format": "npm-run-all format:*",
    "format:js": "prettier --write \"app/**/*.js\"",
    "format:json": "prettier --write \"app/**/*.json\"",
    "format:md": "prettier --write \"**/*.md\"",
    "format:ts": "prettier --write \"app/**/*.ts{,x}\"",
    "lint": "eslint index.js app storybook test --fix --ext .js,.ts,.tsx && npm run format",
    "patch": "patch-package",
    "storybook": "start-storybook -p 9001 -c ./storybook",
    "test": "jest",
    "adb": "adb reverse tcp:9090 tcp:9090 && adb reverse tcp:3000 tcp:3000 && adb reverse tcp:9001 tcp:9001 && adb reverse tcp:8081 tcp:8081",
    "postinstall": "node ./bin/postInstall",
    "build-ios": "react-native bundle --entry-file index.js --platform ios --dev false --bundle-output ios/main.jsbundle --assets-dest ios",
    "build-android": "react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res",
    "clean": "react-native-clean-project",
    "clean-all": "npx react-native clean-project-auto"
  },
  "dependencies": {
    "@kichiyaki/react-native-barcode-generator": "^0.6.7",
    "@react-native-async-storage/async-storage": "^1.14.1",
    "@react-native-google-signin/google-signin": "7.1.0",
    "@react-navigation/bottom-tabs": "^6.2.0",
    "@react-navigation/native": "~6.0.1",
    "@react-navigation/native-stack": "^6.0.2",
    "@react-navigation/stack": "~6.0.1",
    "apisauce": "2.0.0",
    "date-fns": "^2.28.0",
    "expo": "~43.0.0",
    "expo-facebook": "~12.0.3",
    "expo-linear-gradient": "^10.0.3",
    "expo-localization": "11.0.0",
    "expo-modules-core": "^0.4.9",
    "expo-updates": "^0.11.6",
    "i18n-js": "3.8.0",
    "lodash.throttle": "^4.1.1",
    "mobx": "6.1.8",
    "mobx-react-lite": "3.2.0",
    "mobx-state-tree": "5.0.1",
    "qs": "^6.10.3",
    "react": "17.0.2",
    "react-native": "0.67.2",
    "react-native-camera": "^4.2.1",
    "react-native-cli": "^2.0.1",
    "react-native-colo-loco": "^1.0.0",
    "react-native-gesture-handler": "^2.2.0",
    "react-native-image-crop-picker": "^0.37.3",
    "react-native-keychain": "6.2.0",
    "react-native-modal": "^13.0.0",
    "react-native-safe-area-context": "3.1.8",
    "react-native-screens": "3.8.0",
    "react-native-snackbar": "^2.4.0",
    "react-native-svg": "^12.3.0",
    "react-native-vector-icons": "^9.1.0",
    "react-native-webview": "^11.18.1",
    "reactotron-mst": "3.1.4",
    "reactotron-react-js": "^3.3.7",
    "reactotron-react-native": "5.0.1",
    "validate.js": "0.13.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/plugin-proposal-decorators": "7.12.1",
    "@babel/plugin-proposal-optional-catch-binding": "7.12.1",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/cli-platform-ios": "^6.2.0",
    "@rnx-kit/metro-config": "^1.2.26",
    "@rnx-kit/metro-resolver-symlinks": "^0.1.15",
    "@storybook/react-native": "5.3.23",
    "@storybook/react-native-server": "5.3.23",
    "@types/i18n-js": "3.0.3",
    "@types/jest": "26.0.19",
    "@types/react": "17.0.37",
    "@types/react-native": "0.66.9",
    "@types/react-test-renderer": "17.0.1",
    "@typescript-eslint/eslint-plugin": "4.10.0",
    "@typescript-eslint/parser": "4.10.0",
    "babel-jest": "26.6.3",
    "babel-loader": "8.2.2",
    "detox": "19.3.0",
    "eslint": "7.15.0",
    "eslint-config-prettier": "7.0.0",
    "eslint-config-standard": "16.0.2",
    "eslint-plugin-import": "2.22.1",
    "eslint-plugin-node": "11.1.0",
    "eslint-plugin-promise": "4.2.1",
    "eslint-plugin-react": "7.21.5",
    "eslint-plugin-react-native": "3.10.0",
    "expo-modules-autolinking": "^0.3.4",
    "fbjs-scripts": "3.0.0",
    "jest": "26",
    "jest-circus": "26",
    "jest-expo": "^43.0.1",
    "jetifier": "1.6.6",
    "npm-run-all": "4.1.5",
    "patch-package": "6.2.2",
    "postinstall-prepare": "1.0.1",
    "prettier": "2.2.1",
    "query-string": "^7.0.1",
    "react-devtools-core": "4.10.1",
    "react-dom": "^17.0.2",
    "react-native-clean-project": "^3.6.3",
    "react-native-web": "^0.16.3",
    "reactotron-core-client": "^2.8.10",
    "solidarity": "2.3.1",
    "ts-jest": "26",
    "typescript": "4.2.3"
  },
  "prettier": {
    "printWidth": 100,
    "semi": false,
    "singleQuote": false,
    "trailingComma": "all"
  },
  "detox": {
    "test-runner": "jest",
    "configurations": {
      "ios.sim.debug": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/VerifyApp.app",
        "build": "xcodebuild -workspace ios/VerifyApp.xcworkspace -scheme VerifyApp -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build -destination 'name=iPhone 11'",
        "type": "ios.simulator",
        "device": {
          "name": "iPhone 11",
          "os": "iOS 13.2"
        }
      },
      "ios.sim.release": {
        "binaryPath": "ios/build/Build/Products/Release-iphonesimulator/VerifyApp.app",
        "build": "xcodebuild -workspace ios/VerifyApp.xcworkspace -scheme VerifyApp -configuration Release -sdk iphonesimulator -derivedDataPath ios/build -destination 'name=iPhone 11'",
        "type": "ios.simulator",
        "device": {
          "name": "iPhone 11",
          "os": "iOS 13.2"
        }
      }
    }
  },
  "eslintConfig": {
    "root": true,
    "parser": "@typescript-eslint/parser",
    "extends": [
      "plugin:@typescript-eslint/recommended",
      "plugin:react/recommended",
      "plugin:react-native/all",
      "standard",
      "prettier",
      "prettier/@typescript-eslint"
    ],
    "plugins": [
      "@typescript-eslint",
      "react",
      "react-native"
    ],
    "parserOptions": {
      "ecmaFeatures": {
        "jsx": true
      },
      "project": "./tsconfig.json"
    },
    "settings": {
      "react": {
        "pragma": "React",
        "version": "detect"
      }
    },
    "globals": {
      "__DEV__": false,
      "jasmine": false,
      "beforeAll": false,
      "afterAll": false,
      "beforeEach": false,
      "afterEach": false,
      "test": false,
      "expect": false,
      "describe": false,
      "jest": false,
      "it": false
    },
    "rules": {
      "@typescript-eslint/ban-ts-ignore": 0,
      "@typescript-eslint/ban-ts-comment": 0,
      "@typescript-eslint/explicit-function-return-type": 0,
      "@typescript-eslint/explicit-member-accessibility": 0,
      "@typescript-eslint/explicit-module-boundary-types": 0,
      "@typescript-eslint/indent": 0,
      "@typescript-eslint/member-delimiter-style": 0,
      "@typescript-eslint/no-empty-interface": 0,
      "@typescript-eslint/no-explicit-any": 0,
      "@typescript-eslint/no-object-literal-type-assertion": 0,
      "@typescript-eslint/no-var-requires": 0,
      "comma-dangle": 0,
      "multiline-ternary": 0,
      "no-undef": 0,
      "no-unused-vars": 0,
      "no-use-before-define": "off",
      "quotes": 0,
      "react-native/no-raw-text": 0,
      "react/no-unescaped-entities": 0,
      "react/prop-types": "off",
      "space-before-function-paren": 0
    }
  }
} 

Forked On 04 Oct 2022 at 06:04:44

Joshuayoes

There has been a lot of changes since this issue last had activity. We have release a new major version of Ignite, codenamed Maverick. This is going to be closed for now, but please re-open if this still needs attention.

Commented On 04 Oct 2022 at 06:04:44
Issue Comment

Joshuayoes

[Security] update transitive dependency ejs to latest version

please consider to update gluegun to latest version to fix the following security issue: https://github.com/mde/ejs/pull/573

Forked On 04 Oct 2022 at 06:03:16

Joshuayoes

This would be better filed on the gluegun repository.

This security issue doesn't really apply to our use of ejs in Gluegun because we are running our own template code only for the cli users host machine, not on a web server. This is an issue for ejs because users of websites could potentially inject and execute malicious code on web servers that they should not have access to. However, since we only run cli code on the users host machine, there is no target to try to gain elevated privileges on.

Commented On 04 Oct 2022 at 06:03:16
Issue Comment

Frankcalise

Windows Powershell issues

I just dealt with someone who had some problems running under Windows Powershell.

It was worked around by running ignite through good ol' cmd.exe.

The error they were experiencing was:

image

Could have been a rogue globally installed package, Windows Powershell, or perhaps the Illuminati.

Forked On 04 Oct 2022 at 05:58:06

Frankcalise

PowerShell is now working in the latest version of Ignite, v8!

Commented On 04 Oct 2022 at 05:58:06
Issue Comment

Joshuayoes

import model on root-store file from models/index.ts is causing error

What's going on?

When i try to import a model in the root-store file from models/index.ts its throw the following error:

Error: [mobx-state-tree] expected mobx-state-tree type as argument 1, got undefined instead


Steps to reproduce

  1. generate new model: ignite generate model testing
  2. import model in root-store: import { TestingModel } from "../"

if i importing using the following syntax it works: import { TestingModel } from "../testing/testing";

npx ignite-cli doctor results: System platform win32
arch x64
cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz directory myApp D:\Projects\myApp

JavaScript (and globally-installed packages) node 16.11.0 C:\Program Files\nodejs\node.EXE npm 8.0.0 C:\Program Files\nodejs\npm.CMD @nestjs/cli 8.1.4
nest-cli 0.0.5
npm 8.0.0
yarn 1.22.15 C:\Program Files (x86)\Yarn\bin\yarn.CMD depcheck 1.4.2
expo-cli 4.12.11
ignite-cli 7.5.0
pm2 5.1.2

Ignite ignite-cli 7.5.0 C:\Users\lomba\AppData\Local\Yarn\bin\ignite.CMD ignite src build C:\Users\lomba\AppData\Local\Yarn\Data\global\node_modules\ignite-cli\build

Android java 1.8.0_281 C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.EXE android home - C:\Users\lomba\AppData\Local\Android\Sdk

Forked On 04 Oct 2022 at 05:56:08

Joshuayoes

There has been a lot of changes since this issue last had activity. We have release a new major version of Ignite, codenamed Maverick. This is going to be closed for now, but please re-open if this still needs attention.

Commented On 04 Oct 2022 at 05:56:08
Issue Comment

Joshuayoes

Conflict with aws-amplify Auth and API modules (Unhandled promise rejection)

What's going on?

After add AWS amplify (like here https://docs.amplify.aws/start/getting-started/setup/q/integration/react-native/#install-amplify-libraries) and create simple example of signIn and API.get I've got Unhandled promise rejection, [RangeError: Maximum call stack size exceeded.]

Steps to reproduce

  1. Install npx ignite-cli new TobaIgnite --expo
  2. Add aws deps yarn add aws-amplify aws-amplify-react-native @react-native-community/netinfo @react-native-async-storage/async-storage
  3. Create simple Auth.signIn logic
  4. There is an anhandled error

I thought that this is aws-amplify problem, but I created fresh project with react-native-cli and expo-cli and everything was OK, only ignite boilerplate throw errors. Related issue in aws-amplify project: https://github.com/aws-amplify/amplify-js/issues/8957


npx ignite-cli doctor results:

System
  platform           darwin                                                
  arch               x64                                                   
  cpu                4 cores      Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz 
  directory          TobaIgnite   /Users/user/TobaIgnite                   

JavaScript (and globally-installed packages)
  node                         14.15.4      /Users/user/.nvm/versions/node/v14.15.4/bin/node 
  npm                          6.14.10      /Users/user/.nvm/versions/node/v14.15.4/bin/npm  
    @angular/cli               12.0.4                                                        
    @aws-amplify/cli           6.0.1                                                         
    eslint                     7.31.0                                                        
    expo-cli                   4.12.1                                                        
    ignite-cli                 7.5.0                                                         
    json-server                0.16.3                                                        
    ng-up                      3.0.0                                                         
    npm                        6.14.10                                                       
    react-native-cli           2.0.1                                                         
    serverless                 2.60.3                                                        
  yarn                         1.22.5       /usr/local/bin/yarn                              
    bower-away                 1.1.2                                                         
    requirejs-to-webpack-cli   1.0.0                                                         

Ignite
  ignite-cli         7.5.0        /Users/user/.nvm/versions/node/v14.15.4/bin/ignite                        
  ignite src         build        /Users/user/.nvm/versions/node/v14.15.4/lib/node_modules/ignite-cli/build 

Android
  java               13.0.2       /usr/bin/java 
  android home       -            undefined     

iOS
  xcode              13.0       
  cocoapods          1.11.2       /usr/local/bin/pod 

Forked On 04 Oct 2022 at 05:55:04

Joshuayoes

There has been a lot of changes since this issue last had activity. Most notably, we have remove Storybook in our latest Ignite Maverick release, which seemed to be the source of this issue.

This is going to be closed for now, but please re-open if this still needs attention.

Commented On 04 Oct 2022 at 05:55:04