-
Notifications
You must be signed in to change notification settings - Fork 18
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
Wizer failing on marked
NPM package
#280
Comments
Similar problem with |
But for those looking for a working Markdown processor in Spin, markdown-it works great. |
I can reproduce this with a very simple reduced test case: addEventListener('fetch', async (event) => {
"sdf".match(/[\p{L}\p{N}]/u);
}); Not yet sure why this fails: line 2 in that test case works in Firefox's devtools shell and in a standalone SpiderMonkey shell. Will dig in more. |
oooh, I'm pretty sure I know: StarlingMonkey doesn't currently include unicode support, because that's broken in SpiderMonkey's WASI port. Unfortunately there's little we can do about that until that problem is fixed :/ |
I don't know if it is worth capturing errors like this, but..
The
marked
Markedown parser seems to cause a failure in Wizer or Componentize.jsSteps to reproduce:
npm i
and thennpm i marked
spin build --up
Code:
Output:
The text was updated successfully, but these errors were encountered: