[I] ended up having to use an EC2 instance to sort all the dependencies for building, but I'm really happy with how small a patch this ended up requiring.
Originally posted by @G-Rath in #2059 (comment)
Maybe we can make it so that, by default, the JavaScript tools can rely on the last published package of @herb-tools/node-wasm, @herb-tools/node, and @herb-tools/browser so that they don't need to be recompiled from scratch, which requires the full LLVM/clang and the emscripten toolchain.
If somebody wants to work on the parser and/or these packages explicitly, they could opt-in using some kind of flag which then builds these packages from source.
Similarly, with the Ruby gem for just working on the engine or the compiler.
Update the CONTRIBUTING.md accordingly.
Originally posted by @G-Rath in #2059 (comment)
Maybe we can make it so that, by default, the JavaScript tools can rely on the last published package of
@herb-tools/node-wasm,@herb-tools/node, and@herb-tools/browserso that they don't need to be recompiled from scratch, which requires the full LLVM/clang and the emscripten toolchain.If somebody wants to work on the parser and/or these packages explicitly, they could opt-in using some kind of flag which then builds these packages from source.
Similarly, with the Ruby gem for just working on the engine or the compiler.
Update the CONTRIBUTING.md accordingly.