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
Thanks for filing a feature request! Please fill out the TODOs below.
Feature
It seems that the only way to import other packages right now is to vendor them, so I tried to do that by symlinking the dependee
into the dependant deps folder (showing dirs only for conciseness):
error: failed to resolve directory while parsing WIT for path [/Users/mpostma/Documents/code/rust/wasm-experiments/adhoc/wit]
Caused by:
0: failed to parse dependency directory: /Users/mpostma/Documents/code/rust/wasm-experiments/adhoc/wit/deps
1: failed to parse package: /Users/mpostma/Documents/code/rust/wasm-experiments/adhoc/wit/deps/deps
2: no `package` header was found in any WIT file for this package
It seems to be because the second level of deps doesn't contain any WIT file, but only directories.
Benefit
I'm not sure what's the current plan, or the recommended way to deal with imports right now. I suspect that all of this will converge to a more streamlined experience, but until then, it would be nice if we could just symlink components as dependency for other components.
The text was updated successfully, but these errors were encountered:
Thanks for the report! The structure of the wit directory is mostly defined by the wasm-tools project at this time (and doesn't have the greatest documentation unfortunately). You might be interested in bytecodealliance/wasm-tools#1461 and bytecodealliance/wasm-tools#1462 as well.
Overall relaxing various bits of the wit directory are not the easiest thing to do as it needs to be balanced with the variety of consumers of WIT. If possible features like #9288 are intended to help with this, though.
Thanks for filing a feature request! Please fill out the TODOs below.
Feature
It seems that the only way to import other packages right now is to vendor them, so I tried to do that by symlinking the dependee
into the dependant
deps
folder (showing dirs only for conciseness):Then i attempt to generate bindings like so:
and I get the following compile error:
It seems to be because the second level of
deps
doesn't contain anyWIT
file, but only directories.Benefit
I'm not sure what's the current plan, or the recommended way to deal with imports right now. I suspect that all of this will converge to a more streamlined experience, but until then, it would be nice if we could just symlink components as dependency for other components.
The text was updated successfully, but these errors were encountered: