-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] An error occurs when using the codecs in NodeJs #18
Comments
I assume I am completely using this library in the wrong way. And even if would have passed through that point, then further on I would have got the same exception a bit further in the code (whether I set the environment variable or not doesn't matter): My creativity has reached its limit. Hopefully you can illuminate me ;-) |
Ok it seems to work when I don't use
Thanks!! |
Hi @matmen, Thanks for your quick response!!
Ah I wasn't aware of that. Because from the benchmarks on the readme page, I had concluded that WASM was already implemented for encoding and decoding... I am certainly not going to ask an open-source developer for an ETA ;-). But is this something you are working on, or is in the category 'maybe later maybe never'? In the latter case, I need to look for another solution? Which would be a pity, because I don't think there is another wasm solution ...
Are you familiar with Node-RED somehow?
I had hoped to develop a new node that could decode/encode images based on your library and wasm. So I first would decode the jpegs to raw images, then add multiple nodes in a chain that do processing on that raw image, and at the end a node to encode the (processed) raw images back to a jpeg: This way we would only have one decoding, and one encoding. And both based on wasm for better performance. Do you think something like that is a bit realistic? Because I would like to avoid native libraries (like sharp....), because when you e.g. run Node-RED in an (Alpine Linux Docker) there aren't even build tools available. So wasm would be a great alternative ... |
codecs package wasm support is blocked by ongoing imagescript port to rust |
@bartbutenaers Are you currently using ImageScript successfully with Node-RED? Can you offer any guidance in my issue #30? |
@AndreKR, |
@bartbutenaers You might be interested to hear that Node-RED has recently introduced Debian-based images and ImageScript works fine with them. |
Describe the bug
Hi everybody,
I have installed only this:
But when I use afterwards this in a NodeJs program:
Then I get following error:
"Error: todo! (line:18)"
My NodeJs supports wasm, because I use e.g. OpenCv wasm without problems.
To Reproduce
Just call
require("@imagescript/codecs");
in a NodeJs applicationExpected behavior
I don't expect a "TODO" error.
Platform:
Thanks a lot!
Bart
The text was updated successfully, but these errors were encountered: