feat: add dynamic node_module resolution for wasm path

[muenzpraeger]

• Add a test if possible
• Format all commit messages with Conventional Commits

• This PR fixes Can't load shiki vscode-oniguruma in Next 13 react server component #398

[netlify]

✅ Deploy Preview for shiki-matsu ready!

Name	Link
🔨 Latest commit	928814b
🔍 Latest deploy log	https://app.netlify.com/sites/shiki-matsu/deploys/63c14a37cd889d0008db0ddc
😎 Deploy Preview	https://deploy-preview-412--shiki-matsu.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Nedilko]

really waiting you to fix this

[selenecodes]

Same, my react server-side components can't use rehype-pretty-code due to this issue.

[Nedilko]

Same, my react server-side components can't use rehype-pretty-code due to this issue.

as a temporary fix I apply this

[Nedilko]

thanks to @pengx17

[wooorm]

Looks a bit frail to me, perhaps something like import-meta-resolve (but then I’m the author of that)?

[octref]

import-meta-resolve looks good. If all you want is shiki to work with next 13, you can see this sample: https://github.com/shikijs/next-shiki