build a bundle for browser with all deps bundled as well

[inverted-capital]

• [x] 0.0.8 bare obfuscated export of just deps.
  • [ ] stackblitz: replace not a function ?
  • [ ] codesandbox: ?
  • [ ] glitch: ?
  • [ ] terminal: ReferenceError: require is not defined
• [x] 0.0.9 bare unobfuscated export of just deps. Fails in stackblitz, codesandbox, glitch
  • [ ] stackblitz
  • [ ] codesandbox
  • [ ] glitch
• [ ] 0.0.10 bare unobfuscated unoptimized export of just deps.
  • [ ] stackblitz: missing packages
  • [ ] codesandbox: TypeError: Cannot read property 'replace' of undefined
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.11 bare unobfuscated unoptimized export without sodium native
  • [ ] stackblitz: missing packages
  • [ ] codesandbox: process.binding is not supported
  • [ ] glitch: Uncaught ReferenceError: process is not defined
  • [ ] terminal: Error: process.binding is not supported
• [x] 0.0.14 bare unobfuscated unoptimized export without sodium native or tar
  • [x] terminal: working
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [x] codesandbox: ok
  • [ ] glitch: Uncaught ReferenceError: process is not defined

working in all but glitch, as process not available for some reason.

• [x] 0.0.15 add webpack optimization config
  • [ ] terminal:
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [x] codesandbox: ok
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.16 add obfuscator
  • [x] terminal: ok
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [x] codesandbox: ok
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.17 add sodium-native
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [ ] codesandbox: Could not find module in path: 'assert/assert.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.18 remove target: 'node' from webpack.config.js
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [ ] codesandbox: Could not find module in path: 'assert/assert.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.19 set externalsPresets: { web: true } in webpack.config.js (no change)
• [x] 0.0.21 add node polyfills, and use package.json for excludes (no change)
• [x] 0.0.23 remove sodium-native (no change) console logged every bundled library in codeblitz - worked fine, so must be deeper causes that are throwing
• [x] 0.0.24 dual web & node targets in webpack, obfuscator on
  • [x] stackblitz: ok (if install 'events' and 'long')
  • [ ] codesandbox: Could not find module in path: 'util/util.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.25 webpack optimizer back on (no change)
• [x] 0.0.26 full functionality restored
  • [ ] stackblitz: Import error, can't find files: ../../node_modules/is-buffer/index.js
  • [ ] codesandbox: Could not find module in path: 'assert/assert.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.27 node as only webpack target
  • [ ] stackblitz: Import error, can't find files: ../../node_modules/is-buffer/index.js
  • [ ] codesandbox: Could not find module in path: 'assert/assert.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [x] 0.0.28 node polyfill plugin
  • [ ] stackblitz: Import error, can't find files: ../../node_modules/is-buffer/index.js
  • [ ] codesandbox: Could not find module in path: 'util/util.js'
  • [ ] glitch: Uncaught ReferenceError: process is not defined
• [ ] 0.0.29 web target only with vendor bundle
  • [ ] stackblitz:
  • [ ] codesandbox:
  • [ ] glitch:

Seems almost as if no polyfills being added to interblock dependencies by the live editor loaders. Learned that webpack 5 no longer polyfills node basics, but have a plugin to handle this in theory.

In conclusion, running in live editors is harsh to troubleshoot as we cannot see how their bundlers work. It is fair to assume that they expect web compatible modules to be used, tho. The problem appears to be because the live editors are not shimming node internal libraries before rendering in the browser.

Options for further progress:

1. Downgrade to webpack 4
2. Split into browser and server bundles
3. Split out serverside modules such as dynamodb-lock-client into their own packages, to make a pure browser based package
4. Make a vendor bundle with all interblock dependencies bundled in web compatible form - this will test if the live editor bundlers would have been able to bundle this codebase too. Must only obfuscate our primary bundle.
5. Split vendor chunk into multiple pieces to determine offending modules - possibly generate one file per node_module so can know instantly

[inverted-capital]

works for codesandbox - stackblitz has an issue with loading deps of deps, so abandoning