DaddyFrosty/yoga
1
0
Fork 0
Code Issues 96 Pull Requests 31 Actions Packages Projects Releases 33 Wiki Activity

weird error when running test with jest #1777

New Issue
Open
opened 2025-01-06 12:34:49 -08:00 by sibelius · 0 comments
sibelius commented 2025-01-06 12:34:49 -08:00 (Migrated from github.com)
Copy Link

Report

Issues and Steps to Reproduce

failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): BufferSource argument is empty

      at v (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:63:371)

  console.warn
    Aborted(CompileError: WebAssembly.instantiate(): BufferSource argument is empty)

      at v (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:13:60)
      at x (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:63:418)

When running a test in our backend, it is getting this error on yoga-layout

├─┬ @react-pdf/renderer 4.1.6
                                                                            │ └─┬ @react-pdf/layout 4.2.0
                                                                            │   └── yoga-layout 3.2.1

Expected Behavior

it should not error

Actual Behavior

it is breaking

# Report - [x] I have searched [existing issues](https://github.com/facebook/yoga/issues) and this is not a duplicate # Issues and Steps to Reproduce ``` failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): BufferSource argument is empty at v (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:63:371) console.warn Aborted(CompileError: WebAssembly.instantiate(): BufferSource argument is empty) at v (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:13:60) at x (../../node_modules/yoga-layout/dist/binaries/yoga-wasm-base64-esm.js:63:418) ``` When running a test in our backend, it is getting this error on yoga-layout ``` ├─┬ @react-pdf/renderer 4.1.6 │ └─┬ @react-pdf/layout 4.2.0 │ └── yoga-layout 3.2.1 ```` # Expected Behavior it should not error # Actual Behavior it is breaking
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Algorithm
Build and Infrastructure
C#
C++ Enhancement
CLA Signed
Discussion
Documentation
Feature Request
Java
JavaScript
Merged
Question
Reverted
Shared with Meta
Applied via automation to indicate that an Issue or Pull Request has been shared with the team.
YogaKit
YogaLayout ViewGroup
bug
dependencies
Pull requests that update a dependency file
duplicate
enhancement
fb-exported
fh:direct-merge-enabled
invalid
ruby
Pull requests that update Ruby code
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
DaddyFrosty
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DaddyFrosty/yoga#1777
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?