@bravemobile/react-native-code-push 13.1.0-beta.1 → 13.1.0-beta.2

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.
Files changed (5) hide show
  1. package/cli/dist/functions/runExpoBundleCommand.js +4 -0
  2. package/cli/dist/functions/runReactNativeBundleCommand.js +10 -0
  3. package/cli/functions/runExpoBundleCommand.ts +4 -0
  4. package/cli/functions/runReactNativeBundleCommand.ts +10 -0
  5. package/package.json +1 -1
package/cli/dist/functions/runExpoBundleCommand.js CHANGED
@@ -24,6 +24,10 @@ export function runExpoBundleCommand(bundleName, outputPath, platform, sourcemap
24
24
  'false',
25
25
  '--entry-file',
26
26
  entryFile,
27
+ // Same reason as `runReactNativeBundleCommand`: the native build embeds an
28
+ // unminified bundle, and diverging from it inflates every binary patch.
29
+ '--minify',
30
+ 'false',
27
31
  '--platform',
28
32
  platform,
29
33
  '--sourcemap-output',
package/cli/dist/functions/runReactNativeBundleCommand.js CHANGED
@@ -28,6 +28,16 @@ export function runReactNativeBundleCommand(bundleName, outputPath, platform, so
28
28
  'false',
29
29
  '--entry-file',
30
30
  entryFile,
31
+ /**
32
+ * Match React Native's Hermes builds, which disable JS minification. Minifying an
33
+ * update barely changes how large its bytecode is, but it changes how that bytecode
34
+ * is laid out - enough that a binary patch against an unminified binary costs far
35
+ * more than the source change does.
36
+ *
37
+ * Listed before the caller's options so an explicit `--minify` still wins.
38
+ */
39
+ '--minify',
40
+ 'false',
31
41
  '--platform',
32
42
  platform,
33
43
  '--sourcemap-output',
package/cli/functions/runExpoBundleCommand.ts CHANGED
@@ -32,6 +32,10 @@ export function runExpoBundleCommand(
32
32
  'false',
33
33
  '--entry-file',
34
34
  entryFile,
35
+ // Same reason as `runReactNativeBundleCommand`: the native build embeds an
36
+ // unminified bundle, and diverging from it inflates every binary patch.
37
+ '--minify',
38
+ 'false',
35
39
  '--platform',
36
40
  platform,
37
41
  '--sourcemap-output',
package/cli/functions/runReactNativeBundleCommand.ts CHANGED
@@ -38,6 +38,16 @@ export function runReactNativeBundleCommand(
38
38
  'false',
39
39
  '--entry-file',
40
40
  entryFile,
41
+ /**
42
+ * Match React Native's Hermes builds, which disable JS minification. Minifying an
43
+ * update barely changes how large its bytecode is, but it changes how that bytecode
44
+ * is laid out - enough that a binary patch against an unminified binary costs far
45
+ * more than the source change does.
46
+ *
47
+ * Listed before the caller's options so an explicit `--minify` still wins.
48
+ */
49
+ '--minify',
50
+ 'false',
41
51
  '--platform',
42
52
  platform,
43
53
  '--sourcemap-output',
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bravemobile/react-native-code-push",
3
- "version": "13.1.0-beta.1",
3
+ "version": "13.1.0-beta.2",
4
4
  "description": "React Native plugin for the CodePush service",
5
5
  "main": "src/CodePush.js",
6
6
  "react-native": "src/CodePush.js",