Replies: 2 comments
-
Go for it |
Beta Was this translation helpful? Give feedback.
0 replies
-
Feel free to combine! I'm currently using loader in my work with cargo component, but as long as things mostly work the same, I can easily adapt |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As I've been looking at unified publishing (#13) it has become clear to me that my plan to have separate
wasm-pkg-loader
andwasm-pkg-publisher
crates is arbitrary and unhelpful; the two crates would have ended up with nearly identical dependencies and large amounts of code overlap. If there end up being scenarios where a downstream consumer wants to avoid some code associated exclusively with publishing then we can feature flag it out instead.Given that, I'm planning to rename
wasm-pkg-loader
towasm-pkg-client
as part of the publishing implementation. I'd like to just drop thewasm-pkg-loader
crate entirely but if that is going to cause pain for someone already depending on it please comment here and we can look at a more gradual migration.Beta Was this translation helpful? Give feedback.
All reactions