inlined wasm violates chrome webstore no obfuscation policy

[amk-dev]

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Describe the bug

I've been using shiki in my chrome extension. but when i submitted to the chrome webstore i got a violation for obfuscated code.

on looking into it, i found its coming from shiki's inlined wasm. ( i'm using vite )

is there anyway to not include the wasm import in my bundle ?
how can i handle this situation ?

Reproduction

import and use codeToHtml from the full bundle

import { codeToHtml } from "shiki/bundle/full"

Contributes

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests

[antfu]

There is nothing we can do about it, maybe you can try using the JS engine: https://shiki.style/guide/regex-engines#javascript-regexp-engine-experimental be be aware of it's limitations and still experimental