yyyanghj
yyyanghj
> 这里以前有，后面去除了。有特殊过滤需求的可以调用相关接口：`eruda.get('console').filter('log')` 我们是在构建时判断环境变量来注入 eruda, 之前尝试过调用 eruda.get('console').filter('log'), 但是我们只会在 eruda.init 之后调用一次, 不会在业务代码里调用。 这样初始可以过滤出 log, 但是当点击了 Info, Error 之后, 又恢复原样了, 这对于我们来说变成了一次性的过滤。我们没办法来回在 log 和 error 之间切换。
> Would this be useful for places where is embedded, or do are you thinking of this as a feature in the app (tldraw.com)? Thank you for reply. I hope...
see [https://github.com/vuejs/vue-next/pull/3308](https://github.com/vuejs/vue-next/pull/3308)
I got some discovery maybe helpful. I diged the build output of [this reproduction](https://github.com/silvio-e/nuxt-3-7-4), the problem seems to be here. This looks like [@rollup/plugin-wasm code](https://github.com/rollup/plugins/blob/2c58b01a45d31e0abd72c9c83a86c826c898cd24/packages/wasm/src/helper.ts#L5) which is used by nitropack....
https://github.com/nuxt/content/issues/2408#issuecomment-1817630304 Hey guys, a workaround for this issue. ```ts // nuxt.config.ts export default defineNuxtConfig({ nitro: { preset: 'vercel-edge', wasm: { rollup: { targetEnv: 'browser' } } } }) ```
> While this does work, it increases build size **drastically** so be aware of this https://github.com/nuxt/content/issues/2439
related issue https://github.com/nuxt/content/issues/2422