Merge pull request #101 from rootstrap/update-upstream-v6.3.3

chore: update upstream to v6.3.3

Author: asdolo

README.md

@@ -93,6 +93,12 @@ Check this [file](https://github.com/rootstrap/rs-gpt-review/blob/main/.github/w
 - [React Native Svg](https://github.com/software-mansion/react-native-svg)
 - [React Error Boundaries](https://github.com/bvaughn/react-error-boundary)
 - [Expo Image](https://docs.expo.dev/versions/unversioned/sdk/image/)
+- [React Native Keyboard Controller](https://github.com/kirillzyusko/react-native-keyboard-controller)
+- [Moti](https://moti.fyi/)
+- [React Native Safe Area Context](https://github.com/th3rdwave/react-native-safe-area-context)
+- [React Native Screens](https://github.com/software-mansion/react-native-screens)
+- [Tailwind Variants](https://www.tailwind-variants.org/)
+- [Zod](https://zod.dev/)
 
 ## Contributors
 

docs/astro.config.mjs

@@ -146,6 +146,17 @@ export default defineConfig({
             },
           ],
         },
+        {
+          label: 'Recipes',
+          items: [
+            // Each item here is one entry in the navigation menu.
+            {
+              label: 'Sentry Setup',
+              link: '/recipes/sentry-setup/',
+              badge: 'new',
+            },
+          ],
+        },
         {
           label: 'Testing',
           items: [
@@ -186,6 +197,11 @@ export default defineConfig({
           label: 'Libraries Recommendation',
           link: '/libraries-recommendation',
         },
+        {
+          label: 'FAQ',
+          link: '/faq',
+          badge: 'new',
+        },
         {
           label: 'CHANGELOG',
           link: '/changelog',
@@ -194,6 +210,11 @@ export default defineConfig({
           label: 'How to contribute ?',
           link: '/how-to-contribute',
         },
+        {
+          label: 'Reviews',
+          link: '/reviews',
+          badge: 'new',
+        },
         {
           label: 'Stay Updated',
           link: '/stay-updated',

docs/package.json

@@ -10,12 +10,12 @@
     "astro": "astro"
   },
   "dependencies": {
-    "@astrojs/starlight": "^0.21.1",
+    "@astrojs/starlight": "^0.27.1",
     "@expressive-code/plugin-collapsible-sections": "^0.33.4",
     "@expressive-code/plugin-line-numbers": "^0.33.4",
     "@fontsource/ibm-plex-mono": "^5.0.8",
     "@fontsource/ibm-plex-serif": "^5.0.8",
-    "astro": "^4.4.9",
+    "astro": "^4.15.4",
     "hast-util-to-html": "^9.0.0",
     "sharp": "^0.32.3"
   }

docs/pnpm-lock.yaml

@@ -37,7 +37,7 @@ import { Icon } from '@astrojs/starlight/components';
   }
   .container{
     position: absolute;
-    top: 80px;
+    top: 140px;
     left: 50%;
     transform: translate(-50%, 0%);
     background-color: transparent;

docs/src/components/GithubStar.astro

@@ -0,0 +1,51 @@
+---
+title: Frequently asked questions
+description: Frequently asked questions about the React Native / Expo Starter.
+head:
+  - tag: title
+    content: FAQ | React Native / Expo Starter
+---
+
+This page is a collection of frequently asked questions about the React Native / Expo Starter.
+
+### Is this starter for me?
+
+Yes 😀
+
+This starter kit is designed to benefit a wide range of React Native developers, from beginners to experienced professionals. Here's why it might be a good fit for you:
+
+1. **For beginners:** It provides a solid foundation with best practices and common solutions, helping you learn industry-standard approaches to React Native development.
+
+2. **For experienced developers:** It offers a well-structured, production-ready setup that can save you time and effort in project initialization and configuration.
+
+3. **For teams:** It ensures consistency across projects and team members, making it easier to onboard new developers and maintain code quality.
+
+4. **For explorers:** Even if you prefer not to use starter kits, this project can serve as a valuable reference. You can explore the codebase, documentation, and architectural decisions to gain insights and potentially adopt specific solutions for your own projects.
+
+5. **For learners:** The starter kit incorporates up-to-date libraries and patterns, offering an opportunity to familiarize yourself with current best practices in the React Native ecosystem.
+
+6. **For AI-assisted development:** This starter kit works well with AI coding tools. It provides a solid structure and best practices that can guide AI-generated code. This helps ensure that AI assistance leads to high-quality, maintainable code that fits well within your project.
+
+Remember, you don't have to use the entire starter kit as-is. Feel free to cherry-pick ideas, configurations, or code snippets that align with your project needs. Whether you're building a new app from scratch or looking to improve your existing development process, this starter kit can provide valuable insights and practical solutions.
+
+### Why Expo and not React Native CLI?
+
+We have been using Expo as our main framework since the introduction of [Continuous Native Generation (CNG)](https://docs.expo.dev/workflow/continuous-native-generation/) concept and we are happy with the experience.
+
+I think this question is not valid anymore specially after the last React conference when the core react native team recommended using Expo for new projects.
+
+> "As of today, the only recommended community framework for React Native is Expo. Folks at Expo have been investing in the React Native ecosystem since the early days of React Native and as of today, we believe the developer experience offered by Expo is best in class." React native core team
+
+Still hesitating? Check out this [article](https://reactnative.dev/blog/2024/06/25/use-a-framework-to-build-react-native-apps) or this [video](https://www.youtube.com/watch?v=lifGTznLBcw), maybe this one [video](https://www.youtube.com/watch?v=ek_IdGC0G80) too.
+
+### How is behind the starter kit?
+
+This starter kit is maintained by the [Obytes mobile tribe team](https://www.obytes.com/team) since 2021. At Rootstrap we've started using it during 2024. We actively use it for our projects and make slight modifications to better adjust to our workflow, experience and projects. The template is open-source, released under the MIT license, ensuring flexibility for users. Our commitment to this template is ongoing; we will continue to sync it with the Obytes starter kit, maintain it and improve it as long as it remains a core part of our internal development process.
+
+### Can you include X feature or library?
+
+We aim to keep the starter as simple and straightforward as possible. Based on our experience, we believe the current setup provides a solid foundation for most projects.
+
+The starter is opinionated, reflecting our best practices. If you disagree with some of our choices, that's perfectly fine. The starter is designed to be easily customizable to suit your specific needs.
+
+We often receive requests to provide multiple choices for libraries and tools through a CLI. While this may seem appealing, it would significantly increase complexity and maintenance overhead, which we are trying to avoid.

docs/src/content/docs/faq.md

@@ -104,7 +104,7 @@ As mentioned earlier, `zod` is used to validate environment variables at runtime
 ```bash
 ❌ Invalid environment variables: { TEST: [ 'Required' ] }
 ❌ Missing variables in .env.development file, Make sure all required variables are defined in the .env.development file.
-💡 Tip: If you recently updated the .env.development file and the error still persists, try restarting the server with the -cc flag to clear the cache.
+💡 Tip: If you recently updated the .env.development file and the error still persists, try restarting the server with the -c flag to clear the cache.
 ```
 
 :::note[Important]

docs/src/content/docs/getting-started/environment-vars-config.mdx

@@ -31,10 +31,10 @@ pnpm run doctor ## check for any issues with the dependencies you added to your
 pnpm lint ## linting
 pnpm type-check ## type checking
 pnpm test ## tests
-pnpm prebuild -clean ## clean ios and android build folders and regenerate them
+pnpm prebuild --clean ## clean ios and android build folders and regenerate them
 pnpm ios ## run ios build
 pnpm android ## run android build
-pnpm start --cc ## start the server
+pnpm start -c ## start the server
 ```
 
 :::info
@@ -50,7 +50,7 @@ Visit the npm package registry [here](https://www.npmjs.com/package/expo) to ens
 Once you have confirmed that you have the latest version, open your terminal and enter the following command:
 
 ```bash
-pnpm add expo@lastVersion
+pnpm add expo@latest
 ## pnpm add [email protected] for example
 ```
 
@@ -78,10 +78,10 @@ pnpm install ## install new dependencies
 pnpm lint ## linting
 pnpm type-check ## type checking
 pnpm test ## tests
-pnpm prebuild -clean ## clean ios and android build folders and regenerate them
+pnpm prebuild --clean ## clean ios and android build folders and regenerate them
 pnpm ios ## run ios build
 pnpm android ## run android build
-pnpm start --cc ## start the server
+pnpm start -c ## start the server
 ```
 
 Unfortunately, there is no magic trick here in case you have any issues while running your checks, Fixing those errors may require some manual effort. You can start by reading the error message and identifying any relevant packages that may be causing the issue. Check the changelog of those packages to see if there have been any recent updates that might have introduced breaking changes. This will help you to pinpoint the root cause of the issue and take the necessary steps to resolve it.
@@ -144,10 +144,10 @@ pnpm install ## install new dependencies
 pnpm lint ## linting
 pnpm type-check ## type checking
 pnpm test ## tests
-pnpm prebuild -clean ## clean ios and Android build folders and regenerate them
+pnpm prebuild --clean ## clean ios and Android build folders and regenerate them
 pnpm ios ## run ios build
 pnpm android ## run android build
-pnpm start --cc ## start the server
+pnpm start -c ## start the server
 ```
 
 If you are lucky enough and everything works as expected without any issues, you can now update the rest of the dependencies.