-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A few issues in the example directory #70
Comments
Thanks for raising these! Would you be up to opening a PR, or should we make this is as good-first-issue? |
Im happy to open a PR for the tsconfig and npm start but I have no idea where to start with the UTF8 issue |
I think all the example apps are running on CI...? so, what's your node version? |
I was using 14.17.6 If you know what works in CI thatd help too |
https://github.com/open-policy-agent/npm-opa-wasm/actions/runs/1244485210 We're testing with Node 12.x and 14.x |
👍 Ill try specific node and opa versions my OPA was 0.33.1 I tried a local build (using nix) and the release build from GH. I just noticed it says WebAssembly: Unavailable on the one from GH and I'm not confident my local build has actually built with working WebAssembly. I guess I should do a full Also how come deno is added? |
Any OPA binary can produce wasm bundles (which contain the So for this, don't worry about the version output. |
Can you elaborate please? Where's the unexpected appearance? I've recently added linting and formatting using deno in CI, because it seemed like an easy way forward. |
@06kellyjac Did you ever get past this? 😃 |
Sorry. Yeah I couldnt recreate some of the issues. |
I'll clean this up as stale, I hope you don't mind. Feel free to re-open. |
I'm getting
Error: Cannot find module 'utf8'
with bothnodejs-app
andnodejs-ts-app
Also with
nodejs-ts-app
it isn't resolving the type definitions properly so I made these changes to tsconfig:And the docs for
nodejs-ts-app
says to donpm run -- '{\"message\": \"world\"
but that is wrong, it should benpm start -- '{\"message\": \"world\"
The text was updated successfully, but these errors were encountered: