G

Hit this too. @andrewiggins it's complaining about `refs` (plural) which doesn't exist in preact's type file

@marvinhagemeister thank you for looking into this and for the great workaround. Indeed a safari bug. Hoping it gets some attention since it's a general js issue.

Essentially just this (stripped down) webpack.config.js: ``` js module.exports = function () { const config1 = { // ... plugins: [new BundleAnalyzerPlugin()] } const config2 = { // ... plugins:...

+1 Seeing this come in on my live app's crash logs quite often.

Great, good to know! I'd love a plugin (or for webpack proper) to support generating assets for any kind of script url APIs. Figured your name `worker-plugin` could get away...

I was able to do this by creating an App Group and in the launcher set: ```swift UserDefaults(suiteName: "[TeamId][AppGroupId]")?.set(true, forKey: "didLaunchAtLogin") ``` Then in the main app, read that value...

@marvinhagemeister accidental auto-close referencing this PR in a private repo. Not familiar with default vs jsx mode - I'll have to read the source code more and circle back.

@marvinhagemeister I updated it so the jsx renderer is unaffected by applying the normalization after the attribute hook intercepts the standard rendering.

Yea was surprised by it. Here's the proof: React: https://codesandbox.io/s/qx8971z77w Preact: https://codesandbox.io/s/15jxo4x2q

Still `{}` in Preact X: https://codesandbox.io/s/heuristic-bohr-t586n