fix: Add ENV option to allow legacy ssl for newer node versions and our older webpack #84
Conversation
|
|
|
Hi @mitchcapper. This fixes it for Node 18+, but breaks things for Node 16, which is currently the officially supported version used. That's why the build is failing here. Node 16 is still supported by the Node.js team for now, the only issue is that it's not the recommended version for new installs on the website at the moment. I definitely intend to upgrade, but there are issues (nodejs/node#48519) that currently make that impossible in other components, so we're sticking with it for now. Given all that, I think this probably is the right fix, but unless there's some way to make it work for both, it needs to stay unmerged here and wait until we do successfully move to Node 18+ everywhere. That's likely a couple of months from now. In the meantime, if this is a growing issue, maybe it's worth adding a note to the README to point people in the right direction? |
…er webpack Switch to dynamic ENV file for conditional env vars Closes httptoolkit#76
mitchcapper
force-pushed
the
old_webkit_support_newer_node_hack_pr
branch
from
237afc7
to
b71554a
Compare
|
MB I assumed the command line arg would just be ignored by older versions. Switched to using a javascript to generate the ENV file (native support w/ env-cmd) now use the flag conditionally. |
|
Neat! I didn't know env-cmd could do that, that works very nicely, merged 👍 |
|
Oh btw in case you're not aware, HTTP Toolkit Pro is free for contributors. I've just set up an account for the base gmail address from your GH profile (m**.c**@gmail.com). If that'd be useful to you, just click 'Get Pro', then 'Log into existing account' to log in. Thanks for contributing! |
Closes #76