Comments (4)
@DougAnderson444 make sure you are using the latest @bytecodealliance/preview2-shim version 0.0.9. That one does not have features
in the package.json at all.
For the smoke
import this is correct if you have a smoke import in the world. Can you share the output of jco wit component.wasm
for the component you are transpiling, that should show why there is a smoke import there.
If you don't mean to be importing a smoke interface, perhaps you intent to support a component without a "smoke" import?
Imports can be mapped with the custom --map flag - jco transpile x.wasm --map local:smoke=./smoke.js
kind of thing.
from jco.
I think this
import { smokeImports as interface7 } from "smoke"
is supposed to be
import { smokeImports as interface7 } from "./imports/smoke-imports"
But there's only a type definition file smoke-imports.d.ts
and there's no smoke-imports.js
file. Is there supposed to be one?
from jco.
Answering all my own question here today....
- Solved 1 by bringing in the built files into my project folder, then Vite could find the files of course...
- Solved 2 by writing my own
smoke
library with my defined imports and, well, importing it.
🤦♂️
I should have known better, but perhaps this will eventually deserve a doc or blog post.
from jco.
Glad you were able to work through it! Yes we do need better docs and examples, suggestions for how to avoid pitfalls always welcome!
from jco.
Related Issues (20)
- How do I use `js-component-bindgen`? HOT 1
- Incorrect codegen for `wasi:http` resource `RequestOptions` HOT 2
- JCO serve error on composed component HOT 1
- Are TypeScript definitions generated by transpile supposed to include comments from the WIT file? HOT 2
- Validity of file descriptors in the context of the `SyncKit` worker HOT 3
- Unsupported URL wasi when running in Node.js HOT 2
- Transpile bindings for `u32` map to `number` in *.d.ts HOT 3
- Non-conformant exceptions should unwrap as traps HOT 2
- Jco transpile: implementation of wasi-nn for Web HOT 2
- Source phase imports output
- Performance
- JS/WIT Reference
- Lifting `list<borrow<res>>` during transpilation emits invalid code HOT 3
- Resource transferring seems not working with wasi-virt HOT 1
- Crash on startup with an out-of-memory error when environment variables are large HOT 3
- Provide wasm-tools APIs in the browser HOT 2
- `definedResourceTables` codegen generates invalid JS with `--instantiation async` HOT 1
- plain enums are generating complex typescript HOT 8
- Question: `jco types` generating namespaces instead of modules? HOT 1
- Better instantiation workflows
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jco.