You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I figured this would be fixed by the effort to fix #12, but there might also be an easier fix as well, so I'm posting this issue separately.
It seems that the fundamental issue is the native Node loader is invoked not matter what, even if the user explicitly tried to load WasmHighwayHash.
This is because
export { NativeHighwayHash as HighwayHash } from "./native";
is run in index_node.ts not matter what.
The workaround is to directly require the browser/cjs/index_browser.js file.
e.g.
You're right, that is a bug. Thank you for the report. Let me think about how to fix that. Maybe I need to move it to the init stage or delay importing until called 🤔
In the meantime, I pushed out build that includes M1 support. I don't have a M1 mac, so let me know if it works.
When explicitly trying to load and run
WasmHighwayHash
on Mac M1:I am met with
I figured this would be fixed by the effort to fix #12, but there might also be an easier fix as well, so I'm posting this issue separately.
It seems that the fundamental issue is the native Node loader is invoked not matter what, even if the user explicitly tried to load WasmHighwayHash.
This is because
is run in index_node.ts not matter what.
The workaround is to directly require the browser/cjs/index_browser.js file.
e.g.
Which seems to work just fine in my typescript application. YMMV
The text was updated successfully, but these errors were encountered: