fix(JSZipDataAccessHelper): Downgrade JSZip version

[boucaud]

The latest versions of JSZip seem to have broken the JSZipDataAccessHelper.

Calling JSRoot.file().async() returns a promise that never resolves. This breaks .vtkjs loading functionality.

People having the same issue:

Stuk/jszip#724

Stuk/jszip#712

Downgrading to 3.2.0 fixes the issue.

[boucaud]

@floryst What do you think ?

@finetjul @laurentmalka fyi.

[jourdain]

Do we need stream as an added dependency?

[boucaud]

Do we need stream as an added dependency?

Without it we get this error:

ERROR in ../node_modules/jszip/lib/readable-stream-browser.js 9:0-34
Module not found: Error: Can't resolve 'stream' in '[...]/vtk-js/node_modules/jszip/lib'

[floryst]

That should have been covered by the stream-browserify dependency I added, but I guess webpack isn't picking up on it. I did a quick test and the following webpack.common.js patch should work without having to pull in the extra stream dependency.

diff --git a/webpack.common.js b/webpack.common.js
index 44dd277ee5..5b2dd6aa8c 100644
--- a/webpack.common.js
+++ b/webpack.common.js
@@ -97,6 +97,7 @@ const baseConfig = {
     alias: {
       'vtk.js': __dirname,
     },
+    fallback: { "stream": require.resolve("stream-browserify") },
   },
   module: {
     rules: configureVtkRules(),
@@ -148,6 +149,7 @@ const liteConfig = merge(
           'Sources/Rendering/Core/ColorTransferFunction/LiteColorMaps.json'
         ),
       },
+      fallback: { "stream": require.resolve("stream-browserify") },
     },
   },
   baseConfig,

[jourdain]

🎉 This PR is included in version 15.3.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀