Switch to Magick.Native not building

[KnicKnic]

Try to get Magick.Native's build. Which includes more delegates (webp, heic... ). However this one fails

so I abandoning it, just creating the PR for history reasons was supposed to address Issue #46

magick.js:32 exception thrown: RangeError: Invalid typed array length: undefined,RangeError: Invalid typed array length: undefined
    at new Int8Array (<anonymous>)
    at updateGlobalBufferViews (https://knicknic.github.io/imagemagick/test/magick.js:1341:29)
    at _emscripten_resize_heap (https://knicknic.github.io/imagemagick/test/magick.js:8747:7)
    at wasm-function[8949]:64
    at wasm-function[8164]:7263
    at wasm-function[8171]:187
    at wasm-function[8172]:166
    at wasm-function[391]:123
    at wasm-function[1538]:2022
    at wasm-function[1536]:1760
printErr @ magick.js:32
callMain @ magick.js:11246
processFiles @ magick.js:75
onmessage @ magick.js:128

[cancerberoSgx]

I was able to build the magick.* files from their repo, but noticed they didn't have the main() function not the magickWand API which is the high level API. I think this project needs the main() API - the core API is large and complex to use and out of scope for this project IMO.

I guess you were able to generate the files too. Did you try something simpler like just loading them from an html without webworker, or the node.js example ?

Did they have Module['main'] ?

If I compile using this PR scripts should I generate something ?

[KnicKnic]

https://dev.azure.com/oneeyedelf1/wasm-imagemagick/_build/results?buildId=194 Is the results of the one build that passed tests. You can download the artifacts from it(top right) Just so you know there are issues using it, which is why I am not using that PR.