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
walt-cli package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.
Encoding the dependencies into the file is done to ensure the module can be used stand-alone in browser or node. Only the opcodes objects should be necessary for each module.
Goal
Patch the cli wrap function to result in a stripped down version of the modules (without AST information) which can still build but only include the bare minimum buffers in the resulting JS module.
Assuming we strip off AST info from final JS file, how should we test to ensure there is no breakage of any sort. Some suggestions would help for a new person looking into it.
Problem
walt-cli
package when linking multiple .walt files together can "wrap" the modules in a stand-alone JS module. The resulting module is too large because it serialized the dependency tree with the AST information encoded directly into the output, resulting in a massive amount of js.Encoding the dependencies into the file is done to ensure the module can be used stand-alone in browser or node. Only the
opcodes
objects should be necessary for each module.Goal
Patch the cli wrap function to result in a stripped down version of the modules (without AST information) which can still build but only include the bare minimum buffers in the resulting JS module.
Notes
tree
structure to create a run-able Wasm module.The text was updated successfully, but these errors were encountered: