bundo-appgen 0.0.6 → 0.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -160,7 +160,7 @@ We want to wrap a native project as a React Native app host easily without hurti
160
160
 
161
161
  This package is heavily inspired by the [Expo Continuous Native Generation](https://docs.expo.dev/workflow/continuous-native-generation). Expo does a heavy lifting, and can make developers focus more on providing and delivering the actual product.
162
162
 
163
- `bundo-appgen` is also wants to get the same experience like Expo, but the main differentiation from Expo is **keeping each platform configurations separated**, instead of merging the configuration data in a single object configuration. We choose to do this way because it is too difficult to support other platforms such as macOS, and other platforms in a single object. What we mean a single object is `bundo-appgen` provides a configuration for macOS and Windows not within the same kind of data or field, instead `bundo-appgen` provides platform configurations individually. This is much easier for prototyping the native app project because each platform have some unique configurations that other platforms don't have, and we can follow each platform requirements much easier.
163
+ `bundo-appgen` also wants to get the same experience like Expo, but the main differentiation from Expo is **keeping each platform configurations separated**, instead of merging the configuration data in a single object configuration. We choose to do this way because it is too difficult to support other platforms such as macOS, and other platforms in a single object. What we mean a single object is `bundo-appgen` provides a configuration for macOS and Windows not within the same kind of data or field, instead `bundo-appgen` provides platform configurations individually. This is much easier for prototyping the native app project because each platform have some unique configurations that other platforms don't have, and we can follow each platform requirements much easier.
164
164
 
165
165
  For an example, you can see a configuration file example below
166
166
 
package/lib/bin/bin.mjs CHANGED
@@ -989,6 +989,9 @@ ${reactNativeXcodeScriptRelativePath}`
989
989
  }
990
990
  },
991
991
  options: {
992
+ ...appleData.locales?.[0] ? {
993
+ developmentLanguage: appleData.locales[0]
994
+ } : undefined,
992
995
  useBaseInternationalization: false
993
996
  }
994
997
  };
@@ -1082,6 +1085,7 @@ async function main() {
1082
1085
  ...pluginContextResult?.macos.infoPlist
1083
1086
  }
1084
1087
  });
1088
+ console.log("\x1B[1m\x1B[32m✔ Native project has been generated successfully.\x1B[0m");
1085
1089
  }
1086
1090
  var configFileExts = [
1087
1091
  "ts",
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "bundo-appgen",
3
- "version": "0.0.6",
4
- "description": "App generator CLI for React Native macOS",
3
+ "version": "0.0.8",
4
+ "description": "Native app generator for React Native macOS",
5
5
  "license": "MIT",
6
6
  "author": "RakaDoank <rakaaudira@gmail.com> (https://github.com/RakaDoank)",
7
7
  "homepage": "https://github.com/RakaDoank/bundo.rn",
@@ -45,7 +45,7 @@
45
45
  }
46
46
  },
47
47
  "peerDependencies": {
48
- "react-native-macos": "^0.81"
48
+ "react-native-macos": "^0.81 || ^0.83"
49
49
  },
50
50
  "devDependencies": {
51
51
  "typescript": ">=6 <=7",
@@ -198,6 +198,9 @@ export function createProjectSpec(
198
198
  },
199
199
 
200
200
  options: {
201
+ ...(appleData.locales?.[0] ? {
202
+ developmentLanguage: appleData.locales[0],
203
+ } : undefined),
201
204
  useBaseInternationalization: false,
202
205
  },
203
206
 
@@ -46,7 +46,7 @@ import {
46
46
  *
47
47
  * - Init template directory
48
48
  * - Copy the directory
49
- * - Modify template regarding project name and other config related
49
+ * - Modify the template file such as AppDelegate.swift regarding the project name and other configs related
50
50
  * - (Apple)
51
51
  * - Init Asset Catalogs from Config
52
52
  * - (Windows): TODO
@@ -141,6 +141,8 @@ export async function main() {
141
141
  },
142
142
  )
143
143
 
144
+ console.log("\x1b[1m\x1b[32m✔ Native project has been generated successfully.\x1b[0m")
145
+
144
146
  }
145
147
 
146
148
  const configFileExts: string[] = [