Jeremy Spiegel

`electron-builder` (23.3.3) on Windows doesn't seem to be unpacking normal non-symlink node modules for me. Running this should quickly demonstrate the issue: ``` git clone [email protected]:electron/electron-quick-start.git && \ cd electron-quick-start...

I ran into the same issue and found that adding the `com.apple.security.cs.allow-jit` entitlement fixed the issue: ``` com.apple.security.cs.allow-jit ``` This is in the Electron docs at https://www.electronjs.org/docs/latest/tutorial/code-signing#signing--notarizing-macos-builds but didn't seem...

I'm not 100% but I think that Info.plist comes from the downloaded Electron bundle, and it's used as a template and modified by `electron-builder`, so I don't think setting it...

I'll create a Chromium issue as well for this. However, the [specification](https://tools.ietf.org/html/rfc6266#appendix-D) advises to use ASCII rather than ISO-8859-1: ``` Appendix D. Advice on Generating Content-Disposition Header Fields To successfully...

I appreciate your quick response, and I understand wanting to avoid sending extra data for misbehaving clients, but I think this module would be better if by default it followed...

I might be missing something, but I don't actually see the spec use MUST, SHOULD, MAY, etc. in regards to using ISO-8859-1. It seems to only mention ISO-8859-1 when talking...

From the new [spec](https://tools.ietf.org/html/rfc7230#section-3.2.4): ``` Historically, HTTP has allowed field content with text in the ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding. In practice, most...

Fair enough, thank you for that explanation.

A Chromium developer has responded to the [bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1006345): > I'm skeptical that changing behavior here is worth the investment and dealing with the inevitable breakage, unless we want to reach...

👋Hi! Thanks for taking a look! Sorry I missed that branch in your fork before.