@reekon-tools/react-native-pdf-canvas 0.1.0 → 0.1.1

package/dist/index.native.d.ts

@@ -17,5 +17,10 @@
  * synchronously by RN Skia's own import-time side effect, so importing the
  * barrel here is both correct and free of the web ordering hazard. `index.web.ts`
  * installs the CanvasKit-backed resolver instead. See `./skia/skia-api.ts`.
+ *
+ * Both entries are named in `package.json#sideEffects`; a re-export-only
+ * module is otherwise never executed by a tree-shaking bundler and the install
+ * goes with it. Metro does not tree-shake today, so native has never lost it,
+ * but the listing is what makes that a guarantee. See `index.web.ts`.
  */
 export * from './index.js';

package/dist/index.native.js

@@ -17,6 +17,11 @@
  * synchronously by RN Skia's own import-time side effect, so importing the
  * barrel here is both correct and free of the web ordering hazard. `index.web.ts`
  * installs the CanvasKit-backed resolver instead. See `./skia/skia-api.ts`.
+ *
+ * Both entries are named in `package.json#sideEffects`; a re-export-only
+ * module is otherwise never executed by a tree-shaking bundler and the install
+ * goes with it. Metro does not tree-shake today, so native has never lost it,
+ * but the listing is what makes that a guarantee. See `index.web.ts`.
  */
 import { installNativeSkiaResolver } from './skia/resolve.native.js';
 export * from './index.js';

package/dist/index.web.d.ts

@@ -20,5 +20,15 @@
  * `globalThis.CanvasKit`) still gets a working `skiaApi()` without knowing this
  * package has a `./web-init` subpath. `loadPdfCanvasSkiaWeb()` remains the
  * explicit, awaitable route and is what the README points at.
+ *
+ * AND IT ONLY SURVIVES A BUNDLER BECAUSE THIS FILE IS NAMED IN
+ * `package.json#sideEffects`. This module declares no binding of its own —
+ * everything it exports is owned by another module — so under
+ * `"sideEffects": false` Rollup never marked it executed, dropped the call,
+ * and then eliminated the resolver slot it would have filled; every PDF canvas
+ * on the production web build threw `unsupported` on its first raster while
+ * dev (esbuild, which always keeps an entry's top-level code) stayed green.
+ * `__tests__/tree-shaking.test.ts` bundles a consumer of this file and asserts
+ * the install is kept.
  */
 export * from './index.js';

package/dist/index.web.js

@@ -20,6 +20,16 @@
  * `globalThis.CanvasKit`) still gets a working `skiaApi()` without knowing this
  * package has a `./web-init` subpath. `loadPdfCanvasSkiaWeb()` remains the
  * explicit, awaitable route and is what the README points at.
+ *
+ * AND IT ONLY SURVIVES A BUNDLER BECAUSE THIS FILE IS NAMED IN
+ * `package.json#sideEffects`. This module declares no binding of its own —
+ * everything it exports is owned by another module — so under
+ * `"sideEffects": false` Rollup never marked it executed, dropped the call,
+ * and then eliminated the resolver slot it would have filled; every PDF canvas
+ * on the production web build threw `unsupported` on its first raster while
+ * dev (esbuild, which always keeps an entry's top-level code) stayed green.
+ * `__tests__/tree-shaking.test.ts` bundles a consumer of this file and asserts
+ * the install is kept.
  */
 import { installWebSkiaResolver } from './skia/resolve.web.js';
 export * from './index.js';

package/dist/skia/index.native.d.ts

@@ -7,8 +7,12 @@
  *
  * The one thing it adds over the shared barrel is installing the native
  * resolver, so a consumer who imports ONLY this subpath still gets a working
- * `skiaApi()`. The call is a statement using an imported binding, not a bare
- * `import './x.js'` — this package declares `sideEffects: false`, and a bare
- * side-effect import is exactly what that flag licenses a bundler to delete.
+ * `skiaApi()`. The call only survives a bundler because this file is NAMED in
+ * `package.json#sideEffects`: a module that declares no used binding of its
+ * own (this one only re-exports) is otherwise never marked executed by
+ * Rollup, and its top-level statements go with it — a call on an imported
+ * binding is no safer than a bare `import './x.js'`. That is exactly how the
+ * web twin's install was dropped from the production web build once; see
+ * `__tests__/tree-shaking.test.ts`.
  */
 export * from './index.js';

package/dist/skia/index.native.js

@@ -7,9 +7,13 @@
  *
  * The one thing it adds over the shared barrel is installing the native
  * resolver, so a consumer who imports ONLY this subpath still gets a working
- * `skiaApi()`. The call is a statement using an imported binding, not a bare
- * `import './x.js'` — this package declares `sideEffects: false`, and a bare
- * side-effect import is exactly what that flag licenses a bundler to delete.
+ * `skiaApi()`. The call only survives a bundler because this file is NAMED in
+ * `package.json#sideEffects`: a module that declares no used binding of its
+ * own (this one only re-exports) is otherwise never marked executed by
+ * Rollup, and its top-level statements go with it — a call on an imported
+ * binding is no safer than a bare `import './x.js'`. That is exactly how the
+ * web twin's install was dropped from the production web build once; see
+ * `__tests__/tree-shaking.test.ts`.
  */
 import { installNativeSkiaResolver } from './resolve.native.js';
 export * from './index.js';

package/dist/skia/index.web.d.ts

@@ -6,7 +6,9 @@
  * install itself decides nothing: it stores a closure, and
  * `globalThis.CanvasKit` is not read until the first raster.
  *
- * See `index.native.ts` for why this is a statement and not a bare
- * `import './resolve.web.js'`.
+ * This file is named in `package.json#sideEffects`, and must stay there: it
+ * declares no binding of its own, so without the listing Rollup never marks it
+ * executed and the install below is dropped. See `index.native.ts` and
+ * `__tests__/tree-shaking.test.ts`.
  */
 export * from './index.js';

package/dist/skia/index.web.js

@@ -6,8 +6,10 @@
  * install itself decides nothing: it stores a closure, and
  * `globalThis.CanvasKit` is not read until the first raster.
  *
- * See `index.native.ts` for why this is a statement and not a bare
- * `import './resolve.web.js'`.
+ * This file is named in `package.json#sideEffects`, and must stay there: it
+ * declares no binding of its own, so without the listing Rollup never marks it
+ * executed and the install below is dropped. See `index.native.ts` and
+ * `__tests__/tree-shaking.test.ts`.
  */
 import { installWebSkiaResolver } from './resolve.web.js';
 export * from './index.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reekon-tools/react-native-pdf-canvas",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "PDF pages as Skia images, drawn at exact doc-space rects inside somebody else's transform. Owns no canvas, no gestures, no viewport state.",
   "author": "REEKON Tools",
   "license": "MIT",
@@ -12,7 +12,17 @@
     "access": "public"
   },
   "type": "module",
-  "sideEffects": false,
+  "//sideEffects": "NOT `false`. The four entry files below are `export *` re-exports plus a top-level resolver install, and a bundler applies `sideEffects` to the IMPORTED module: with `false`, Rollup never marks a module that declares no used binding as executed and drops the call (that is what broke every PDF canvas on the production web build while dev — esbuild, entry-point code always kept — stayed green). `src/**` is listed so the property is testable against source; see `__tests__/tree-shaking.test.ts`. `web-init` is not listed: its install is inside an exported function.",
+  "sideEffects": [
+    "./dist/index.web.js",
+    "./dist/index.native.js",
+    "./dist/skia/index.web.js",
+    "./dist/skia/index.native.js",
+    "./src/index.web.ts",
+    "./src/index.native.ts",
+    "./src/skia/index.web.ts",
+    "./src/skia/index.native.ts"
+  ],
   "//files-scripts": "`scripts` ships because the peer-floor check runs from a CONSUMER'S postinstall, before/without any build of `dist`.",
   "//files": "`*.podspec` SHIPS OR iOS IS SILENTLY ABSENT. Autolinking reads the podspec out of the INSTALLED package, so a podspec that is not in this list means `pod install` finds nothing, `PdfCanvas` never appears in Podfile.lock, and `NativeModules.PdfCanvas` is undefined at runtime with no build error anywhere. `ios/Package.swift` and `ios/Tests` ship as part of `ios` and cost a few KB; they are what lets a consumer run the core's host tests against the exact version they installed.",
   "files": [