{"id":20195537,"url":"https://github.com/dev-rem/divic-shippex-test","last_synced_at":"2025-10-16T14:15:26.023Z","repository":{"id":243035654,"uuid":"811282689","full_name":"Dev-Rem/divic-shippex-test","owner":"Dev-Rem","description":null,"archived":false,"fork":false,"pushed_at":"2024-06-06T09:58:25.000Z","size":396,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-01-13T19:27:43.196Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Dev-Rem.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-06-06T09:46:14.000Z","updated_at":"2024-06-06T09:58:28.000Z","dependencies_parsed_at":"2024-06-06T11:19:42.361Z","dependency_job_id":"27155fa1-38df-4d02-b033-b09d25449240","html_url":"https://github.com/Dev-Rem/divic-shippex-test","commit_stats":null,"previous_names":["dev-rem/divic-shippex-test"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dev-Rem%2Fdivic-shippex-test","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dev-Rem%2Fdivic-shippex-test/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dev-Rem%2Fdivic-shippex-test/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dev-Rem%2Fdivic-shippex-test/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Dev-Rem","download_url":"https://codeload.github.com/Dev-Rem/divic-shippex-test/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":241629772,"owners_count":19993710,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-14T04:18:03.022Z","updated_at":"2025-10-16T14:15:20.976Z","avatar_url":"https://github.com/Dev-Rem.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Welcome to your Expo app 👋\n\nThis is an [Expo](https://expo.dev) project created with [`create-expo-app`](https://www.npmjs.com/package/create-expo-app).\n\n## Get started\n\n1. Install dependencies\n\n   ```bash\n   npm install\n   ```\n\n2. Start the app\n\n   ```bash\n    npx expo start\n   ```\n\nIn the output, you'll find options to open the app in a\n\n- [development build](https://docs.expo.dev/develop/development-builds/introduction/)\n- [Android emulator](https://docs.expo.dev/workflow/android-studio-emulator/)\n- [iOS simulator](https://docs.expo.dev/workflow/ios-simulator/)\n- [Expo Go](https://expo.dev/go), a limited sandbox for trying out app development with Expo\n\nYou can start developing by editing the files inside the **app** directory. This project uses [file-based routing](https://docs.expo.dev/router/introduction).\n\n## Get a fresh project\n\nWhen you're ready, run:\n\n```bash\nnpm run reset-project\n```\n\nThis command will move the starter code to the **app-example** directory and create a blank **app** directory where you can start developing.\n\n## Learn more\n\nTo learn more about developing your project with Expo, look at the following resources:\n\n- [Expo documentation](https://docs.expo.dev/): Learn fundamentals, or go into advanced topics with our [guides](https://docs.expo.dev/guides).\n- [Learn Expo tutorial](https://docs.expo.dev/tutorial/introduction/): Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.\n\n## Join the community\n\nJoin our community of developers creating universal apps.\n\n- [Expo on GitHub](https://github.com/expo/expo): View our open source platform and contribute.\n- [Discord community](https://chat.expo.dev): Chat with Expo users and ask questions.\n\nBuilding an APK Using EAS Build\nSteps to Build an APK\nSet Up Your Expo Project\n\nMake sure your Expo project is set up and you have installed all dependencies.\n\n```bash\nnpm install\nInstall EAS CLI\n```\n\nIf you haven't already, install the EAS CLI globally on your machine.\n\n```bash\nnpm install -g eas-cli\n```\n\nConfigure Your Project for EAS\n\nRun the following command to configure your project for EAS builds.\n\n```bash\neas build:configure\n```\n\nThis command will guide you through setting up your eas.json file, which contains the configuration for your builds.\n\nCreate a Build Profile\n\nIn your project root, you'll have an eas.json file. Ensure you have a build profile for Android. Your eas.json might look like this:\n\n```json\n{\n  \"build\": {\n    \"production\": {\n      \"android\": {\n        \"buildType\": \"apk\"\n      }\n    }\n  }\n}\n```\n\nLogin to Expo\n\nEnsure you are logged in to your Expo account.\n\n```bash\neas login\n```\nStart the Build\n\nInitiate the build process. You can specify the profile you want to use (e.g., production).\n\n```bash\neas build --platform android --profile production\n```\nHandle Credentials\n\nEAS CLI will guide you through setting up the credentials for your build. You can let EAS handle it for you, or you can provide your own keystore if you have one.\n\nMonitor the Build\n\nOnce the build process starts, you can monitor the progress in your terminal. You can also view the build progress on the Expo dashboard.\n\nDownload the APK\n\nAfter the build completes, you'll receive a URL to download the APK. You can also find the APK on the Expo dashboard under your project.\n\nTest the APK\n\nDownload the APK to your Android device or emulator and test it to ensure everything is working as expected.\n\nAdditional Configuration (Optional)\nUsing Environment Variables\nYou can use environment variables in your eas.json to manage different build configurations. Here's an example:\n\n```json\n{\n  \"build\": {\n    \"production\": {\n      \"android\": {\n        \"buildType\": \"apk\",\n        \"env\": {\n          \"API_URL\": \"https://api.production.example.com\"\n        }\n      }\n    }\n  }\n}\n```\nCustomizing Build Scripts\nYou can add custom scripts to run before or after the build by specifying them in your eas.json.\n\n```json\n\n{\n  \"build\": {\n    \"production\": {\n      \"android\": {\n        \"buildType\": \"apk\",\n        \"hooks\": {\n          \"preBuild\": \"echo Running pre-build script...\",\n          \"postBuild\": \"echo Running post-build script...\"\n        }\n      }\n    }\n  }\n}\n```\nReferences and Further Reading\nExpo EAS Build Documentation\nExpo CLI Reference\nEAS Build Profiles\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdev-rem%2Fdivic-shippex-test","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdev-rem%2Fdivic-shippex-test","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdev-rem%2Fdivic-shippex-test/lists"}