Package tar@3.0.0 (latest) broke unpack.js
ZaDarkSide opened this issue · comments
node_modules\wndb-with-exceptions\unpack.js:52
.pipe(tar.Extract({ path: __dirname }))
^
TypeError: tar.Extract is not a function
at extractTarball (F:\Repositories\iris-bot-engine.git\node_modules\wndb-with-exceptions\unpack.js:52:15)
at Object.<anonymous> (F:\Repositories\iris-bot-engine.git\node_modules\wndb-with-exceptions\unpack.js:58:1)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:420:7)
at startup (bootstrap_node.js:139:9)
tar@2.2.1
was the last version compatible with unpack.js
In tar@3.0.0
method tar.Extract
was renamed tar.x
see:
tar@2.2.1
=> tar.js vs tar@3.0.0
=> tar.js
You are using tar@latest
in package.json it should be tar@2.2.1
+1
Updated original post with more info.
+1
+1
+1
Please accept the pull request from @laalex to fix this issue.
Should be fixed in 3.1.3 -- publishing shortly. Sorry for delay.