Use writeBinaryToPath instead of require('fs').writeFileSync

[chrisbaume]

👋 Hello! I tried to import the browser package into a React Native project, but got the following error:

The package at "node_modules/@willwade/aac-processors/dist/browser/processors/gridsetProcessor.js" attempted to import the Node standard library module "fs".
It failed because the native React runtime does not include the Node standard library.
Learn more
  1617 |             const zipBuffer = await zip.generateAsync({ type: 'uint8array' });
  1618 |             // eslint-disable-next-line @typescript-eslint/no-var-requires
> 1619 |             require('fs').writeFileSync(outputPath, zipBuffer);
       |                      ^
  1620 |             return;
  1621 |         }
  1622 |         // Collect all unique styles from pages and buttons

Import stack:

 node_modules/@willwade/aac-processors/dist/browser/processors/gridsetProcessor.js
 | import "fs"

 node_modules/@willwade/aac-processors/dist/browser/index.browser.js
 | import "./processors/gridsetProcessor"

 app/index.tsx
 | import "@willwade/aac-processors/browser"

I'm not familiar with the codebase, but I can see that src/index.browser.ts imports src/processors/gridsetProcessor, which includes require('fs'). I wonder whether that should be using writeBinaryToPath from src/utils/io instead, as is used elsewhere?

[willwade]

Yeah for sure - I recently did a huge refactor to deal with dual publishing (node and cjs). This is clearly something I lost...