You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click the terminal icon, pick preview to build and launch the test in the browser to the right. Use Terminal icon in the browser to open the browser console.
In the log: Uncaught TypeError: Cannot read properties of undefined (reading 'rawintegrationparameters_new').
Using Vite.js 5.0.12, Pixi.js 7.4.0 and Rapier.js 0.12. With Rapier at 0.11.2 it works fine and running in watch works fine for 0.12. As watch works, guessing something has to be updated with Vite, any info on what might have changed to cause this issue?
The text was updated successfully, but these errors were encountered:
Worked around the issue by using rapier2d-compat instead. Like this to keep chunks as when using rapier2d. import("@dimforge/rapier2d-compat").then(module => module.init().then(() => { this.rapier = module; // ... }));
I am also facing same issue, everything works fine in development but issue comes in build and after preview. I am using latest rapier 0.14.0 version and vite 6.1.0
You can use 0.14. Either you use rapier2d-compat instead or, in your vite.config.ts file, you can set treeshake: false. This setting is under build -> rollupOptions. When 0.14.1 is released you can enable treeshake again.
I created a minimal example here https://codesandbox.io/p/sandbox/rapierbuild-n3q2l6.
Click the terminal icon, pick preview to build and launch the test in the browser to the right. Use Terminal icon in the browser to open the browser console.
In the log: Uncaught TypeError: Cannot read properties of undefined (reading 'rawintegrationparameters_new').
Using Vite.js 5.0.12, Pixi.js 7.4.0 and Rapier.js 0.12. With Rapier at 0.11.2 it works fine and running in watch works fine for 0.12. As watch works, guessing something has to be updated with Vite, any info on what might have changed to cause this issue?
The text was updated successfully, but these errors were encountered: