rspack icon indicating copy to clipboard operation
rspack copied to clipboard

[Bug]: runtime bundle throws exception in Safari. TypeError: undefined is not an object (evaluating e[n].call).

Open fredrik-lindqvist opened this issue 1 year ago • 2 comments

System Info

System: OS: macOS 14.2.1, CPU: Apple M2 pro Memory: 16gb Shell: 5.9 - /bin/zsh Binaries: Node: 20.10.0 npm: 10.8.2 Browsers: Chrome 121.0.6167.160 Safari 18.0 npmPackages: @rspack/cli: 1.0.8 @rspack/core: 1,0.8 @swc/core: 1.7.26

Details

When running production build in safari 18.0 our app crashes and shows only white screen and in the console an error shows "TypeError: undefined is not an object (evaluating e[n].call)" thrown from our rspack run-time bundle. If we downgrade to 0.7.5 our production build works just fine in safari.

Reproduce link

No response

Reproduce Steps

  1. run production build.
  2. Open app in safari 18 and runtime bundle should throw an TypeError.

fredrik-lindqvist avatar Sep 30 '24 08:09 fredrik-lindqvist

Hello @fredrik-lindqvist, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by need reproduction will be closed if no activities in 14 days.

github-actions[bot] avatar Oct 02 '24 07:10 github-actions[bot]

Hello @fredrik-lindqvist, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by need reproduction will be closed if no activities in 14 days.

github-actions[bot] avatar Oct 02 '24 07:10 github-actions[bot]

I've seen this as well, but it is almost impossible to debug. Sometimes the built bundle does this, sometimes it doesn't, and it is very hard to nail down when.

What I can say is that we've had to pin rspack packages to 1.0.0-beta.1 which works. Anything after that breaks, but not in a way I've been able to reproduce consistently.

Given that the behavior would change somewhat randomly between installing different packages, my feeling was that this was somehow a swc-core issue at the root, but I was unable to verify that.

connebs avatar Oct 09 '24 21:10 connebs

Since the issue was labeled with need reproduction, but no response in 14 days. This issue will be closed. Feel free to comment and reopen it if you have any further questions.

github-actions[bot] avatar Oct 25 '24 00:10 github-actions[bot]