zees-dev
zees-dev
+1 for this too... Still waiting on this - been pretty much a year. The [medium article](https://medium.com/myetherwallet/ethvm-the-open-source-ethereum-blockchain-explorer-powered-by-mew-f17fc4d74f0a) does not at all hint at an incomplete solution.
You can disable the UI via the optional `doc=False` parameter: `api = Api(app, doc=False)` Source: https://flask-restplus.readthedocs.io/en/0.8.2/swaggerui.html
If you're using `vite` you can use this plugin to polyfill for node: https://github.com/sodatea/vite-plugin-node-stdlib-browser ```ts // vite.config.ts import { defineConfig } from 'vite'; import nodePolyfills from 'vite-plugin-node-stdlib-browser' export default defineConfig({...
Is there a roadmap on when this shall be possible?
Was looking into the same functionality - especially for wasm-in-wasm context where I'd like to pass an import directly from the browser runtime directly through the host wasm to the...
Do we need to update the `transaction_version` in the runtime - since we've added all the pallet call index macros?
we should also run all benchmarks again; due to code/algorithmic optimizations, weights could be reduced in some cases (i'd assume)
@leo-plugdefi can we address the conflicts for another round of reviews.
needs to be rebased (conflicts)
> How does the migration do on the production data? I was curious if this is subject to similar issues to the one we saw on the last fpass migration...