Skip to content
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

Linking failure in asm.js: Unexpected stdlib member #1627

Closed
cduff opened this issue Nov 30, 2021 · 6 comments
Closed

Linking failure in asm.js: Unexpected stdlib member #1627

cduff opened this issue Nov 30, 2021 · 6 comments

Comments

@cduff
Copy link

cduff commented Nov 30, 2021

Introducing @react-pdf/renderer to my project has resulted in warning messages in my Jest test outputs, like:

(node:29756) V8: C:\project\node_modules\@react-pdf\yoga\src\build\Release\nbind.js:1781 Linking failure in asm.js: Unexpected stdlib member

I've created a minimal reproduction repo: https://github.com/cduff/react-pdf-linking-failure

Any idea how these can be resolved?

@cduff
Copy link
Author

cduff commented Nov 30, 2021

Could be related to facebook/yoga#898 although the error message report by the OP there was a bit different.

@jeetiss
Copy link
Collaborator

jeetiss commented Dec 7, 2021

Hi @cduff

I think the warning is here from the start of the time

It would be nice to fix this, but the error doesn't break anything, so it is not a priority now

@cduff
Copy link
Author

cduff commented Dec 7, 2021

Hi @cduff

I think the warning is here from the start of the time

It would be nice to fix this, but the error doesn't break anything, so it is not a priority now

Hi @jeetiss,

Yes, those warnings look related.

It's true that the error doesn't appear to break anything, but having Jest output polluted with error messages is quite annoying, e.g.

image

Therefore, I think it would be ideal for this to be resolved.

@ghost
Copy link

ghost commented Jul 19, 2022

Is there any update on this. I'm also getting this in jest tests.

@edmofro
Copy link

edmofro commented Sep 22, 2022

Has anyone fixed this, or at least found a way to silence that specific error to avoid spamming the test output?

@jeetiss
Copy link
Collaborator

jeetiss commented Jan 28, 2023

fixed in #2105

@jeetiss jeetiss closed this as completed Jan 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants