bundo-appgen 0.0.5 → 0.0.7

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
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bundo-appgen",
3
- "version": "0.0.5",
3
+ "version": "0.0.7",
4
4
  "description": "App generator CLI for React Native macOS",
5
5
  "license": "MIT",
6
6
  "author": "RakaDoank <rakaaudira@gmail.com> (https://github.com/RakaDoank)",
@@ -10,6 +10,16 @@
10
10
  "url": "https://github.com/RakaDoank/bundo.rn.git",
11
11
  "directory": "packages/bundo-appgen"
12
12
  },
13
+ "keywords": [
14
+ "bundo",
15
+ "bundo.rn",
16
+ "react",
17
+ "react-native",
18
+ "react-native-macos",
19
+ "macos",
20
+ "app generator",
21
+ "cross-platform"
22
+ ],
13
23
  "scripts": {
14
24
  "build": "bun ./_scripts/build.mts",
15
25
  "build-types": "bunx tsc --project ./tsconfig.build-types.json"
@@ -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