joshuayoes Github contribution chart
joshuayoes Github Stats
joshuayoes Most Used Languages

Activity

01 Dec 2022

Issue Comment

Joshuayoes

Compiling JS Failed using `@rnx-kit/metro-serializer-esbuild`

What happened?

In Ignite, we currently have @rnx-kit/metro-resolver-symlinks integrated into our vanilla react-native workflow. We would like to experiment with adding @rnx-kit/metro-serializer-esbuild to get faster compilation and tree shaking.

However, I have been getting cryptic build errors when attempting to run the dev server

See PR for more logs: https://github.com/infinitered/ignite/pull/1984


Attempted changes:

Affected Package

@rnx-kit/metro-serializer-esbuild

Version

0.1.17

Which platforms are you seeing this issue on?

  • [ ] Android
  • [X] iOS
  • [ ] macOS
  • [ ] Windows

System Information

npx ignite-cli doctor
System
  platform           darwin                                                  
  arch               arm64                                                   
  cpu                10 cores      Apple M1 Max                              
  directory          boilerplate   /Users/joshuayoes/Code/ignite/boilerplate 

JavaScript (and globally-installed packages)
  node                      16.16.0                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/node 
  npm                       7.24.2                                    /Users/joshuayoes/Code/ignite/node_modules/.bin/npm      
    eas-cli                 2.7.0                                                                                              
    expo-cli                6.0.6                                                                                              
    react-devtools-inline   4.26.1                                                                                             
    react-devtools          4.26.0                                                                                             
    sharp-cli               2.1.1                                                                                              
  yarn                      1.22.19                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/yarn 
  pnpm                      7.5.2                                     /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/pnpm 
                            <no pnpm global package info available>                                                            
  expo                      46.0.17                                   managed                                                  

Ignite
  ignite-cli         8.4.2        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               11.0.16.1    /Users/joshuayoes/.asdf/shims/java    
  android home       -            /Users/joshuayoes/Library/Android/sdk 

iOS
  xcode              13.4.1     
  cocoapods          1.11.3       /Users/joshuayoes/.asdf/shims/pod 

Tools
  git                git version 2.37.3   /opt/homebrew/bin/git 

Steps to Reproduce

Pull down Ignite repo

git clone https://github.com/infinitered/ignite.git
cd ignite 

Checkout PR https://github.com/infinitered/ignite/pull/1984

git checkout rnx-kit-esbuild 

The Ignite repository has a cli in the root directory, but a fully functioning react-app in the boilerplate directory. Checkout, and start running

cd boilerplate
yarn install
yarn start
yarn ios 

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

Forked On 01 Dec 2022 at 08:00:02

Joshuayoes

Ah I see, that is good to know. It looks like they treeshaking as a part of their swcpack package, but it's still in development

Commented On 01 Dec 2022 at 08:00:02
Issue Comment

Joshuayoes

Compiling JS Failed using `@rnx-kit/metro-serializer-esbuild`

What happened?

In Ignite, we currently have @rnx-kit/metro-resolver-symlinks integrated into our vanilla react-native workflow. We would like to experiment with adding @rnx-kit/metro-serializer-esbuild to get faster compilation and tree shaking.

However, I have been getting cryptic build errors when attempting to run the dev server

See PR for more logs: https://github.com/infinitered/ignite/pull/1984


Attempted changes:

Affected Package

@rnx-kit/metro-serializer-esbuild

Version

0.1.17

Which platforms are you seeing this issue on?

  • [ ] Android
  • [X] iOS
  • [ ] macOS
  • [ ] Windows

System Information

npx ignite-cli doctor
System
  platform           darwin                                                  
  arch               arm64                                                   
  cpu                10 cores      Apple M1 Max                              
  directory          boilerplate   /Users/joshuayoes/Code/ignite/boilerplate 

JavaScript (and globally-installed packages)
  node                      16.16.0                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/node 
  npm                       7.24.2                                    /Users/joshuayoes/Code/ignite/node_modules/.bin/npm      
    eas-cli                 2.7.0                                                                                              
    expo-cli                6.0.6                                                                                              
    react-devtools-inline   4.26.1                                                                                             
    react-devtools          4.26.0                                                                                             
    sharp-cli               2.1.1                                                                                              
  yarn                      1.22.19                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/yarn 
  pnpm                      7.5.2                                     /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/pnpm 
                            <no pnpm global package info available>                                                            
  expo                      46.0.17                                   managed                                                  

Ignite
  ignite-cli         8.4.2        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               11.0.16.1    /Users/joshuayoes/.asdf/shims/java    
  android home       -            /Users/joshuayoes/Library/Android/sdk 

iOS
  xcode              13.4.1     
  cocoapods          1.11.3       /Users/joshuayoes/.asdf/shims/pod 

Tools
  git                git version 2.37.3   /opt/homebrew/bin/git 

Steps to Reproduce

Pull down Ignite repo

git clone https://github.com/infinitered/ignite.git
cd ignite 

Checkout PR https://github.com/infinitered/ignite/pull/1984

git checkout rnx-kit-esbuild 

The Ignite repository has a cli in the root directory, but a fully functioning react-app in the boilerplate directory. Checkout, and start running

cd boilerplate
yarn install
yarn start
yarn ios 

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

Forked On 01 Dec 2022 at 06:31:10

Joshuayoes

Have you considered looking into swc? https://swc.rs/docs/configuration/compilation It is possible we may still be able to get similar speed gains, but have a more feature complete compiler for es5 code.

Commented On 01 Dec 2022 at 06:31:10
Issue Comment

Joshuayoes

Compiling JS Failed using `@rnx-kit/metro-serializer-esbuild`

What happened?

In Ignite, we currently have @rnx-kit/metro-resolver-symlinks integrated into our vanilla react-native workflow. We would like to experiment with adding @rnx-kit/metro-serializer-esbuild to get faster compilation and tree shaking.

However, I have been getting cryptic build errors when attempting to run the dev server

See PR for more logs: https://github.com/infinitered/ignite/pull/1984


Attempted changes:

Affected Package

@rnx-kit/metro-serializer-esbuild

Version

0.1.17

Which platforms are you seeing this issue on?

  • [ ] Android
  • [X] iOS
  • [ ] macOS
  • [ ] Windows

System Information

npx ignite-cli doctor
System
  platform           darwin                                                  
  arch               arm64                                                   
  cpu                10 cores      Apple M1 Max                              
  directory          boilerplate   /Users/joshuayoes/Code/ignite/boilerplate 

JavaScript (and globally-installed packages)
  node                      16.16.0                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/node 
  npm                       7.24.2                                    /Users/joshuayoes/Code/ignite/node_modules/.bin/npm      
    eas-cli                 2.7.0                                                                                              
    expo-cli                6.0.6                                                                                              
    react-devtools-inline   4.26.1                                                                                             
    react-devtools          4.26.0                                                                                             
    sharp-cli               2.1.1                                                                                              
  yarn                      1.22.19                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/yarn 
  pnpm                      7.5.2                                     /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/pnpm 
                            <no pnpm global package info available>                                                            
  expo                      46.0.17                                   managed                                                  

Ignite
  ignite-cli         8.4.2        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               11.0.16.1    /Users/joshuayoes/.asdf/shims/java    
  android home       -            /Users/joshuayoes/Library/Android/sdk 

iOS
  xcode              13.4.1     
  cocoapods          1.11.3       /Users/joshuayoes/.asdf/shims/pod 

Tools
  git                git version 2.37.3   /opt/homebrew/bin/git 

Steps to Reproduce

Pull down Ignite repo

git clone https://github.com/infinitered/ignite.git
cd ignite 

Checkout PR https://github.com/infinitered/ignite/pull/1984

git checkout rnx-kit-esbuild 

The Ignite repository has a cli in the root directory, but a fully functioning react-app in the boilerplate directory. Checkout, and start running

cd boilerplate
yarn install
yarn start
yarn ios 

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

Forked On 01 Dec 2022 at 06:15:08

Joshuayoes

Thanks for taking a look at this! That is good to know that I should consider mainly using this plugin when bundling instead of on the dev server.

Commented On 01 Dec 2022 at 06:15:08

Joshuayoes

chore(package.json): update all rnxkit libraries

Pushed On 30 Nov 2022 at 08:20:24

Joshuayoes

fix(babel|metro.config.js): add preset options from docs

https://microsoft.github.io/rnx-kit/docs/tools/metro-serializer-esbuild#usage

Pushed On 30 Nov 2022 at 08:20:24

Joshuayoes

refactor(app): replace export * to enable tree-shaking

https://microsoft.github.io/rnx-kit/docs/tools/metro-serializer-esbuild#known-limitations

Pushed On 30 Nov 2022 at 08:20:24

Joshuayoes

feat(types): add react-native-web

Created On 30 Nov 2022 at 06:17:23

Joshuayoes

started

Started On 30 Nov 2022 at 05:01:34
Issue Comment

Joshuayoes

npx react-native run-ios fail on ignite-cli v8.3.1, node lts v14.20.0

Describe the bug

What happened? I tried to use expo-47-rn-70 in the project. then Could not run sample project created with "npx react-native run-ios" command.

npx react-native run-ios

 ** BUILD FAILED **

The following build commands failed:
	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
	CompileSwift normal x86_64
(2 failures) 

Ignite version

8.3.1

Additional info

npx ignite-cli doctor

 System
  platform           darwin                                                  
  arch               x64                                                     
  cpu                8 cores      Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz 
  directory          iosBuild     /Users/xxxp/Desktop/iosBuild   

JavaScript (and globally-installed packages)
  node               14.20.0      /usr/local/bin/node 
  npm                6.14.17      /usr/local/bin/npm                  
    @vue/cli         5.0.6                            
  yarn               1.22.19      /usr/local/bin/yarn 
  pnpm               -            not installed       
  expo               47.0.3       managed             

Ignite
  ignite-cli         8.3.1        /Users/xxxp/Desktop/node/node_cache/_npx/6972/bin/ignite                        
  ignite src         build        /Users/xxxp/Desktop/node/node_cache/_npx/6972/lib/node_modules/ignite-cli/build 

Android
  java               -            not installed 
  android home       -            undefined     

iOS
  xcode              12.4       
  cocoapods          1.11.3       /usr/local/bin/pod 

Tools
  git                git version 2.27.0   /usr/local/bin/git 

Forked On 30 Nov 2022 at 12:07:55

Joshuayoes

Running a fresh app using yarn run ios fails wiht the message: "error No simulator available with name 'iPhone 13'", but using yarn run expo:ios works, and also using Xcode (Simulator iPhone 14 / iOS 16.1) to run the app works ok too.

The issue you are having is known, try this solution here: https://github.com/infinitered/ignite/issues/2170#issuecomment-1249641608

Commented On 30 Nov 2022 at 12:07:55

Joshuayoes

fix(expo-web): dev server resolution, added link routing (#2303 by @frankcalise)

  • fix(boilerplate): podfile lock hermes version mismatch

  • vendor(boilerplate): added expo linking, resolve web dev server issue

  • fix(boilerplate): make web links usable

  • fix(boilerplate): added placeholder scheme for linking

  • Update boilerplate/app/screens/DemoShowroomScreen/DemoShowroomScreen.tsx

Co-authored-by: Yulian Glukhenko yulian@infinite.red

  • Update boilerplate/app/screens/DemoShowroomScreen/DemoShowroomScreen.tsx

Co-authored-by: Yulian Glukhenko yulian@infinite.red

Co-authored-by: Yulian Glukhenko yulian@infinite.red

Pushed On 28 Nov 2022 at 05:37:00

Joshuayoes

chore(release): 8.4.1 [skip ci]

8.4.1 (2022-11-21)

Bug Fixes

Pushed On 28 Nov 2022 at 05:37:00

Joshuayoes

fix(boilerplate): Simplifies Toggle's switch-variant to not require measuring logic. Adds icon customization to Toggle's checkbox-variant. (#2315 by @yulolimum)

Pushed On 28 Nov 2022 at 05:37:00

Joshuayoes

chore(release): 8.4.2 [skip ci]

8.4.2 (2022-11-21)

Bug Fixes

  • boilerplate: Simplifies Toggle's switch-variant to not require measuring logic. Adds icon customization to Toggle's checkbox-variant. (#2315 by @yulolimum) (c6181c4)

Pushed On 28 Nov 2022 at 05:37:00

Joshuayoes

feat(bin): add zx based generators

Pushed On 28 Nov 2022 at 05:37:00

Joshuayoes

refactor(generate): add fileName and ext for consistency

Pushed On 28 Nov 2022 at 05:37:00
Started

Joshuayoes

started

Started On 28 Nov 2022 at 04:47:37

Joshuayoes

started

Started On 28 Nov 2022 at 04:47:10

Joshuayoes

started

Started On 25 Nov 2022 at 06:35:22
Issue Comment

Joshuayoes

esbuild: Moving to @rnx-kit/metro-serializer-esbuild

This is an experimental PR, demoing Ignite using @rnx-kit/metro-serializer-esbuild.

Main benefits:

  • Tree shaking (smaller JS bundles)
  • Faster compilation (maybe?)

More info is here: https://github.com/microsoft/rnx-kit/issues/1743

This is not ready to merge, as we need to test out the changes recommended by @tido64 and @afoxman in that thread, and also figure out if this will work with the Expo/Vanilla unification efforts (#1983). Also make sure it works on Expo web.

Forked On 23 Nov 2022 at 02:14:57

Joshuayoes

Maybe related to transform? https://app.circleci.com/pipelines/github/infinitered/ignite/2345/workflows/1a9dcabd-0e60-4e66-888c-a45b52413157/jobs/2923

yarn run v1.22.18
$ jest
PASS src/tools/demo.test.ts (6.496 s)
PASS src/tools/packager.test.ts (6.564 s)
PASS test/vanilla/ignite-help.test.ts (13.407 s)
PASS test/vanilla/ignite-remove-demo.test.ts (13.847 s)
PASS test/vanilla/ignite-generate.test.ts (17.333 s)
FAIL test/vanilla/ignite-new.test.ts (163.38 s)
  ● ignite new › ignite new Foo --debug --packager=npm --yes --use-cache › should be able to use `generate` command and have pass output pass npm run test, npm run lint, and npm run compile scripts

    Command failed: cd /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo && npm run test && cd /mnt/ramdisk/repo
    FAIL app/services/api/apiProblem.test.ts
      ● Test suite failed to run

        Jest encountered an unexpected token

        This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

        By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

        Here's what you can do:
         • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
         • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
         • If you need a custom transformation specify a "transform" option in your config.
         • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

        You'll find more details and examples of these config options in the docs:
        https://jestjs.io/docs/en/configuration.html

        Details:

        /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo/node_modules/react-native/jest/setup.js:384
        import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
        ^^^^^^

        SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1350:14)
      FAIL app/models/Episode.test.ts
        ● Test suite failed to run
          Jest encountered an unexpected token
          This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
          By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
          Here's what you can do:
           • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
           • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
           • If you need a custom transformation specify a "transform" option in your config.
           • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
          You'll find more details and examples of these config options in the docs:
          https://jestjs.io/docs/en/configuration.html
          Details:
          /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo/node_modules/react-native/jest/setup.js:384
          import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
          ^^^^^^
          SyntaxError: Cannot use import statement outside a module
      FAIL app/models/ModTest.test.ts
        ● Test suite failed to run
          Jest encountered an unexpected token
          This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
          By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
          Here's what you can do:
           • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
           • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
           • If you need a custom transformation specify a "transform" option in your config.
           • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
          You'll find more details and examples of these config options in the docs:
          https://jestjs.io/docs/en/configuration.html
          Details:
          /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo/node_modules/react-native/jest/setup.js:384
          import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
          ^^^^^^
          SyntaxError: Cannot use import statement outside a module
      FAIL app/utils/storage/storage.test.ts
        ● Test suite failed to run
          Jest encountered an unexpected token
          This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
          By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
          Here's what you can do:
           • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
           • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
           • If you need a custom transformation specify a "transform" option in your config.
           • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
          You'll find more details and examples of these config options in the docs:
          https://jestjs.io/docs/en/configuration.html
          Details:
          /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo/node_modules/react-native/jest/setup.js:384
          import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
          ^^^^^^
          SyntaxError: Cannot use import statement outside a module
      FAIL test/i18n.test.ts
        ● Test suite failed to run
          Jest encountered an unexpected token
          This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
          By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
          Here's what you can do:
           • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/ecmascript-modules for how to enable it.
           • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
           • If you need a custom transformation specify a "transform" option in your config.
           • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
          You'll find more details and examples of these config options in the docs:
          https://jestjs.io/docs/en/configuration.html
          Details:
          /tmp/ignite-2b3598c3647caa65c46ae0008d3b291c/Foo/node_modules/react-native/jest/setup.js:384
          import _classCallCheck from "@babel/runtime/helpers/classCallCheck";
          ^^^^^^
          SyntaxError: Cannot use import statement outside a module
      Test Suites: 5 failed, 5 total
      Tests:       0 total
      Snapshots:   0 total
      Time:        2.294 s
      Ran all test suites.

Test Suites: 1 failed, 5 passed, 6 total
Tests:       1 failed, 23 passed, 24 total
Snapshots:   18 passed, 18 total
Time:        164.196 s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Exited with code exit status 1 

Commented On 23 Nov 2022 at 02:14:57
Issue Comment

Joshuayoes

esbuild: Moving to @rnx-kit/metro-serializer-esbuild

This is an experimental PR, demoing Ignite using @rnx-kit/metro-serializer-esbuild.

Main benefits:

  • Tree shaking (smaller JS bundles)
  • Faster compilation (maybe?)

More info is here: https://github.com/microsoft/rnx-kit/issues/1743

This is not ready to merge, as we need to test out the changes recommended by @tido64 and @afoxman in that thread, and also figure out if this will work with the Expo/Vanilla unification efforts (#1983). Also make sure it works on Expo web.

Forked On 23 Nov 2022 at 02:13:35

Joshuayoes

Updated this branch, and updated past @rnx-kit/metro-serializer-esbuild@0.1.11.

Getting a cryptic build error that I'm not getting on master


Reproducible steps

In ignite directory

cd boilerplate
yarn install
yarn start
yarn ios 

Simulator output

yarn ios output

➜  boilerplate git:(rnx-kit-esbuild) ✗ yarn ios
yarn run v1.22.19
$ react-native run-ios
info Found Xcode workspace "HelloWorld.xcworkspace"
info Building (using "xcodebuild -workspace HelloWorld.xcworkspace -configuration Debug -scheme HelloWorld -destination id=EB879DB3-0643-4C14-9F28-71C879883890")
success Successfully built the app
2022-11-22 17:28:08.361 xcodebuild[56638:1782885] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-11-22 17:28:08.361 xcodebuild[56638:1782885] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:6E1C3CCB-9DCA-442C-A939-5B600D3343C0, OS:15.5, name:iPhone 8 }
{ platform:iOS Simulator, id:B928C239-4174-4985-A6C3-5BF84DDDB1A0, OS:15.5, name:iPhone 8 Plus }
{ platform:iOS Simulator, id:76B47B7D-137F-40F2-9140-586FF9709A3A, OS:15.5, name:iPhone 11 }
{ platform:iOS Simulator, id:00049CD8-CD76-4A5A-92CF-5B63ACB9B001, OS:15.5, name:iPhone 11 Pro }
{ platform:iOS Simulator, id:5D67ED71-E53F-4B7C-A55B-A9C42CB3C651, OS:15.5, name:iPhone 11 Pro Max }
{ platform:iOS Simulator, id:6899559E-F18D-45E6-86F0-9526BEBC4F3D, OS:15.5, name:iPhone 12 }
{ platform:iOS Simulator, id:B58A56DE-4A43-464F-B50E-BE7CF9BFE371, OS:15.5, name:iPhone 12 Pro }
{ platform:iOS Simulator, id:3E5C2AE6-E279-4FBC-9D1A-0F10113D2D40, OS:15.5, name:iPhone 12 Pro Max }
{ platform:iOS Simulator, id:7FB2BEBD-713D-4139-8CA7-3DACC2B9C582, OS:15.5, name:iPhone 12 mini }
{ platform:iOS Simulator, id:EB879DB3-0643-4C14-9F28-71C879883890, OS:15.5, name:iPhone 13 }
{ platform:iOS Simulator, id:6B1EE194-DBDC-442C-A644-8FA8D3CC5C73, OS:15.5, name:iPhone 13 Pro }
{ platform:iOS Simulator, id:B0A520DC-66F9-4996-9A54-3BB47B867A44, OS:15.5, name:iPhone 13 Pro Max }
{ platform:iOS Simulator, id:AC7C8D9B-CCC6-4BBD-828E-CE4CCF8261C9, OS:15.5, name:iPhone 13 mini }
{ platform:iOS Simulator, id:03ED2AC9-124E-4FF3-9C5A-4F29FB3F109F, OS:15.5, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:1491DD81-80B1-4F48-AB7A-ADA360FA36AA, OS:15.5, name:iPod touch (7th generation) }
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00006001-000C68243C04401E }
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:44863323-18A6-404C-AF5F-4C27F8164CCA, OS:15.5, name:iPad (9th generation) }
{ platform:iOS Simulator, id:A2BA173E-B775-436F-B031-A6CD595BD575, OS:15.5, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:0EC836CB-4915-4EA6-93CE-E73F167E5E19, OS:15.5, name:iPad Pro (9.7-inch) }
{ platform:iOS Simulator, id:59140F8D-AD0A-48D3-B8D0-97DC37A3DB9C, OS:15.5, name:iPad Pro (11-inch) (3rd generation) }
{ platform:iOS Simulator, id:AB23D9DD-6C0F-4F81-BEB1-CD1325BA0F8B, OS:15.5, name:iPad Pro (12.9-inch) (5th generation) }
{ platform:iOS Simulator, id:DCAF7560-6E18-4E12-B624-091F56943625, OS:15.5, name:iPad mini (6th generation) }
info Installing "/Users/joshuayoes/Library/Developer/Xcode/DerivedData/HelloWorld-bqhwxjdhmfoghtghcplopzwwglsb/Build/Products/Debug-iphonesimulator/HelloWorld.app"
info Launching "com.helloworld"
success Successfully launched the app on the simulator
✨  Done in 5.26s. 

npx ignite-cli doctor output

npx ignite-cli doctor
System
  platform           darwin                                                  
  arch               arm64                                                   
  cpu                10 cores      Apple M1 Max                              
  directory          boilerplate   /Users/joshuayoes/Code/ignite/boilerplate 

JavaScript (and globally-installed packages)
  node                      16.16.0                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/node 
  npm                       7.24.2                                    /Users/joshuayoes/Code/ignite/node_modules/.bin/npm      
    eas-cli                 2.7.0                                                                                              
    expo-cli                6.0.6                                                                                              
    react-devtools-inline   4.26.1                                                                                             
    react-devtools          4.26.0                                                                                             
    sharp-cli               2.1.1                                                                                              
  yarn                      1.22.19                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/yarn 
  pnpm                      7.5.2                                     /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/pnpm 
                            <no pnpm global package info available>                                                            
  expo                      46.0.17                                   managed                                                  

Ignite
  ignite-cli         8.4.2        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               11.0.16.1    /Users/joshuayoes/.asdf/shims/java    
  android home       -            /Users/joshuayoes/Library/Android/sdk 

iOS
  xcode              13.4.1     
  cocoapods          1.11.3       /Users/joshuayoes/.asdf/shims/pod 

Tools
  git                git version 2.37.3   /opt/homebrew/bin/git 

Commented On 23 Nov 2022 at 02:13:35

Joshuayoes

fix(metro.config.js): remove require to conditional blocks

Pushed On 23 Nov 2022 at 01:39:32
Issue Comment

Joshuayoes

npx react-native run-ios fail on ignite-cli v8.3.1, node lts v14.20.0

Describe the bug

What happened? I tried to use expo-47-rn-70 in the project. then Could not run sample project created with "npx react-native run-ios" command.

npx react-native run-ios

 ** BUILD FAILED **

The following build commands failed:
	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
	CompileSwift normal x86_64
(2 failures) 

Ignite version

8.3.1

Additional info

npx ignite-cli doctor

 System
  platform           darwin                                                  
  arch               x64                                                     
  cpu                8 cores      Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz 
  directory          iosBuild     /Users/xxxp/Desktop/iosBuild   

JavaScript (and globally-installed packages)
  node               14.20.0      /usr/local/bin/node 
  npm                6.14.17      /usr/local/bin/npm                  
    @vue/cli         5.0.6                            
  yarn               1.22.19      /usr/local/bin/yarn 
  pnpm               -            not installed       
  expo               47.0.3       managed             

Ignite
  ignite-cli         8.3.1        /Users/xxxp/Desktop/node/node_cache/_npx/6972/bin/ignite                        
  ignite src         build        /Users/xxxp/Desktop/node/node_cache/_npx/6972/lib/node_modules/ignite-cli/build 

Android
  java               -            not installed 
  android home       -            undefined     

iOS
  xcode              12.4       
  cocoapods          1.11.3       /usr/local/bin/pod 

Tools
  git                git version 2.27.0   /usr/local/bin/git 

Forked On 23 Nov 2022 at 01:32:37

Joshuayoes

I'm getting the same thing on my machine:

In ignite directory

cd boilerplate
yarn install
yarn start
yarn ios 

Simulator output

yarn ios output

➜  boilerplate git:(rnx-kit-esbuild) ✗ yarn ios
yarn run v1.22.19
$ react-native run-ios
info Found Xcode workspace "HelloWorld.xcworkspace"
info Building (using "xcodebuild -workspace HelloWorld.xcworkspace -configuration Debug -scheme HelloWorld -destination id=EB879DB3-0643-4C14-9F28-71C879883890")
success Successfully built the app
2022-11-22 17:28:08.361 xcodebuild[56638:1782885] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-11-22 17:28:08.361 xcodebuild[56638:1782885] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
{ platform:iOS Simulator, id:6E1C3CCB-9DCA-442C-A939-5B600D3343C0, OS:15.5, name:iPhone 8 }
{ platform:iOS Simulator, id:B928C239-4174-4985-A6C3-5BF84DDDB1A0, OS:15.5, name:iPhone 8 Plus }
{ platform:iOS Simulator, id:76B47B7D-137F-40F2-9140-586FF9709A3A, OS:15.5, name:iPhone 11 }
{ platform:iOS Simulator, id:00049CD8-CD76-4A5A-92CF-5B63ACB9B001, OS:15.5, name:iPhone 11 Pro }
{ platform:iOS Simulator, id:5D67ED71-E53F-4B7C-A55B-A9C42CB3C651, OS:15.5, name:iPhone 11 Pro Max }
{ platform:iOS Simulator, id:6899559E-F18D-45E6-86F0-9526BEBC4F3D, OS:15.5, name:iPhone 12 }
{ platform:iOS Simulator, id:B58A56DE-4A43-464F-B50E-BE7CF9BFE371, OS:15.5, name:iPhone 12 Pro }
{ platform:iOS Simulator, id:3E5C2AE6-E279-4FBC-9D1A-0F10113D2D40, OS:15.5, name:iPhone 12 Pro Max }
{ platform:iOS Simulator, id:7FB2BEBD-713D-4139-8CA7-3DACC2B9C582, OS:15.5, name:iPhone 12 mini }
{ platform:iOS Simulator, id:EB879DB3-0643-4C14-9F28-71C879883890, OS:15.5, name:iPhone 13 }
{ platform:iOS Simulator, id:6B1EE194-DBDC-442C-A644-8FA8D3CC5C73, OS:15.5, name:iPhone 13 Pro }
{ platform:iOS Simulator, id:B0A520DC-66F9-4996-9A54-3BB47B867A44, OS:15.5, name:iPhone 13 Pro Max }
{ platform:iOS Simulator, id:AC7C8D9B-CCC6-4BBD-828E-CE4CCF8261C9, OS:15.5, name:iPhone 13 mini }
{ platform:iOS Simulator, id:03ED2AC9-124E-4FF3-9C5A-4F29FB3F109F, OS:15.5, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:1491DD81-80B1-4F48-AB7A-ADA360FA36AA, OS:15.5, name:iPod touch (7th generation) }
{ platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00006001-000C68243C04401E }
{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
{ platform:iOS Simulator, id:44863323-18A6-404C-AF5F-4C27F8164CCA, OS:15.5, name:iPad (9th generation) }
{ platform:iOS Simulator, id:A2BA173E-B775-436F-B031-A6CD595BD575, OS:15.5, name:iPad Air (5th generation) }
{ platform:iOS Simulator, id:0EC836CB-4915-4EA6-93CE-E73F167E5E19, OS:15.5, name:iPad Pro (9.7-inch) }
{ platform:iOS Simulator, id:59140F8D-AD0A-48D3-B8D0-97DC37A3DB9C, OS:15.5, name:iPad Pro (11-inch) (3rd generation) }
{ platform:iOS Simulator, id:AB23D9DD-6C0F-4F81-BEB1-CD1325BA0F8B, OS:15.5, name:iPad Pro (12.9-inch) (5th generation) }
{ platform:iOS Simulator, id:DCAF7560-6E18-4E12-B624-091F56943625, OS:15.5, name:iPad mini (6th generation) }
info Installing "/Users/joshuayoes/Library/Developer/Xcode/DerivedData/HelloWorld-bqhwxjdhmfoghtghcplopzwwglsb/Build/Products/Debug-iphonesimulator/HelloWorld.app"
info Launching "com.helloworld"
success Successfully launched the app on the simulator
✨  Done in 5.26s. 

npx ignite-cli doctor output

npx ignite-cli doctor
System
  platform           darwin                                                  
  arch               arm64                                                   
  cpu                10 cores      Apple M1 Max                              
  directory          boilerplate   /Users/joshuayoes/Code/ignite/boilerplate 

JavaScript (and globally-installed packages)
  node                      16.16.0                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/node 
  npm                       7.24.2                                    /Users/joshuayoes/Code/ignite/node_modules/.bin/npm      
    eas-cli                 2.7.0                                                                                              
    expo-cli                6.0.6                                                                                              
    react-devtools-inline   4.26.1                                                                                             
    react-devtools          4.26.0                                                                                             
    sharp-cli               2.1.1                                                                                              
  yarn                      1.22.19                                   /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/yarn 
  pnpm                      7.5.2                                     /Users/joshuayoes/.asdf/installs/nodejs/16.16.0/bin/pnpm 
                            <no pnpm global package info available>                                                            
  expo                      46.0.17                                   managed                                                  

Ignite
  ignite-cli         8.4.2        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite      
  ignite src         build        /Users/joshuayoes/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build 

Android
  java               11.0.16.1    /Users/joshuayoes/.asdf/shims/java    
  android home       -            /Users/joshuayoes/Library/Android/sdk 

iOS
  xcode              13.4.1     
  cocoapods          1.11.3       /Users/joshuayoes/.asdf/shims/pod 

Tools
  git                git version 2.37.3   /opt/homebrew/bin/git 

Commented On 23 Nov 2022 at 01:32:37

Joshuayoes

Initial Maverick branch

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Merge branch 'master' into maverick

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Default Splash Screen Implementation; Splash Screen Generator (#1965)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Removes storybook; Updates Text, Button, and Screen components; Starts updating theming. (#1992)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Runs linter on boilerplate.

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

More linting fixes.

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

More linting fixes.

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

fix(boilerplate): defined children props for Text, Button

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

fix(screen): fixed arguments for onContentSizeChange

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

chore: moved TODO to make linter happy

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

RN/Expo Unite! (#1985)

  • feat(boilerplate): unified vanilla and expo build

  • feat(commands): reworked new for unified flow

  • feat(commands): updated help to remove expo switch

  • chore: removed expo related tests

  • fix(new): const in favor of let

  • chore(boilerplate): linter updates

  • vendor(expo-constants): downgrade to remove ios warning

  • fix(boilerplate): unified metro and babel configs

  • fix(boilerplate): fixed some deps as per expo doctor

  • fix(metro-config): fixing issue with Expo metro config setup

  • fix(new): added expo dep warning, fixed log message

  • fix(boilerplate): fix expo-font version and app.tsx for expo

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Adds Crash Reporting boilerplate (#1996)

  • feat(utils): initial crash reporting boilerplate

  • fix(crash-reporting): early exit from reporting in dev

  • fix(crash-reporting): reworked early return

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Merge branch 'master' into maverick

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

feature(maverick): initial demo screen (#2002)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Updates components: Icon, AutoImage. Removes components: Wallpaper, Gradient. (#2004)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

feat(generators): Add front matter support to generator templates (#1630 by @kateinkim)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

docs: Navigation / styling documentation (#1980 by @silasjmatson and @jamonholmgren)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

Adds observer to navigator, other navigator cleanup (#2005 by @jamonholmgren)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

docs(readme): #1924 added more troubleshooting tips (#2006)

Pushed On 23 Nov 2022 at 12:32:12

Joshuayoes

docs: Expanded generator template docs, front matter docs (#2008 by @jamonholmgren)

Pushed On 23 Nov 2022 at 12:32:12
Issue Comment

Joshuayoes

feat(generators): support for component subdirectory

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
    • [x] No subdirectory passes
    • [ ] Subdirectory generated, needs relative paths back to "./Text" and "../theme"
  • [x] README.md has been updated with your changes, if relevant

Describe your PR

  • Closes #1746
  • Supports components to be generated in a subdirectory
  • Supplies frontmatter props with subdirectory (to extend other templates)
  • Added test to check the output of both root components and subdirectory nested components
  • Updated documentation for new prop

image

image

Forked On 23 Nov 2022 at 12:21:38

Joshuayoes

I wrote another draft PR of an idea to make implementing this easier: https://github.com/infinitered/ignite/pull/2317

If we go with using a tool like zx with generators, this could potentially thrown in the ignite cookbook

Commented On 23 Nov 2022 at 12:21:38
Issue Comment

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Forked On 19 Nov 2022 at 12:46:35

Joshuayoes

Other interesting zx features of note:

Commented On 19 Nov 2022 at 12:46:35
Issue Comment

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Forked On 19 Nov 2022 at 12:43:30

Joshuayoes

This PR does not have the splash-screen or app-icon generator implemented, but I wanted to get some feedback about the reaction of this approach before implementing more sophisticated scripts like that

Commented On 19 Nov 2022 at 12:43:30

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Forked On 19 Nov 2022 at 12:41:17

Joshuayoes

`zx` can be used with typescript, but it seems to take a lot wrangling to set it up. However, the existing globals have nice type defs already. And we can use jsdoc to create types otherwise. Another approach here may be to add `.d.ts` files and import them using `jsdoc`
On 19 Nov 2022 at 12:41:17

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Merged On 19 Nov 2022 at 12:41:17

Joshuayoes

Commented On 19 Nov 2022 at 12:41:17

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Forked On 19 Nov 2022 at 12:39:17

Joshuayoes

Instead of using template literals for file strings, I decided to go with doing a regex replace. This was for a few reasons: - using template literal syntax breaks [syntax highlighting from this extension](https://marketplace.visualstudio.com/items?itemName=zjcompt.es6-string-javascript) - I find it's hard to read A trade off is that it's not immediately obvious which strings are variables in a template string. But I still find it to be pretty readable, and one can always use Ctrl+F to see what is getting find and replaced
On 19 Nov 2022 at 12:39:17

Joshuayoes

feat(bin): add zx based generators

Please verify the following:

  • [ ] yarn test jest tests pass with new tests, if relevant
  • [ ] README.md has been updated with your changes, if relevant

Describe your PR

There is a scripting tool called zx that is a hybrid between bash and node scripting. It has a lot of dev experience and productivity of gluegun.

To play around with it, I decided to implement some of the existing generators in ignite. This was relatively simple to do. And with this extension, you can even get syntax highlighting with the js strings.

This may be a nice alternative API for generators so that ignite users can update these scripts as a project grows.

Initially, I thought about creating an alternative typescript generator API that I create a proof of concept of. But the nice thing about using zx is that it would pretty much remove any maintenance cost with generators from ignite. Additionally, these scripts are portable, so they can dropped into existing projects.

I will leave this PR here for discussion and an artifact of that exploration

Merged On 19 Nov 2022 at 12:39:18

Joshuayoes

Commented On 19 Nov 2022 at 12:39:18

Joshuayoes

refactor(generate): add fileName and ext for consistency

Pushed On 19 Nov 2022 at 12:33:03

Joshuayoes

feat(bin): add zx based generators

Created On 19 Nov 2022 at 12:28:00
Create Branch
Joshuayoes In infinitered/ignite Create Branchfeat/zx

Joshuayoes

Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more!

On 19 Nov 2022 at 12:23:21

Joshuayoes

fix(react-native-web/tsconfig.json): remove trailing comma

Pushed On 18 Nov 2022 at 03:03:52

Joshuayoes

feat(types): add react-native-web

Created On 18 Nov 2022 at 02:58:50

Joshuayoes

feat(react-native-web): prettier formatting

Pushed On 18 Nov 2022 at 02:53:57