create-remix fails behind proxy

What version of Remix are you using?

1.4.3

Steps to Reproduce

Run npx create-remix when you are behind a corporate proxy.

Expected Behavior

create-remix should work, either getting proxy config from environment variables or allowing users to pass it as a parameter.

Actual Behavior

After answering the questions, the installation fails with the following message:

>npx create-remix
Need to install the following packages:
  create-remix
Ok to proceed? (y) y
? Where would you like to create your app? ./my-remix-app
? What type of app do you want to create? Just the basics
? Where do you want to deploy? Choose Remix if you're unsure; it's easy to change deployment targets. Remix App Server
? Do you want me to run `npm install`? No
| Creating your app…request to https://codeload.github.com/remix-run/remix/tar.gz/main failed, reason: connect ETIMEDOUT 20.201.28.149:443

I confirmed the problem is actually proxy config by modifying the function downloadAndExtractTarball in node_modules\@remix-run\dev\cli\create.js. I just added my proxy config hard-coded with the help of https-proxy-agent package. With the following change create-remix succeeded.

var HttpsProxyAgent = require('https-proxy-agent');

async function downloadAndExtractTarball(projectDir, url, {
  token,
  filePath
}) {
  const proxyAgent = new HttpsProxyAgent('http://my.proxy.server:3128');
  let response = await fetch__default["default"](url, token ? {
    agent: proxyAgent,
    headers: {
      Authorization: `token ${token}`
    }
  } : {
    agent: proxyAgent
  });
  // rest of the method
}

[rrgomide]

Please, guys. Fix this. It also happened to me. I think this is extremely important to be fixed since we’re trying to incorporate Remix on enterprise-level projects.

There are a lot of companies that use corporate proxies for security and we just can’t disable it.

My solution was to scaffold a Remix project at home and bring all files to the company, which is really annoying.

[machour]

@rdscott-vrsk Apologies, this should have been closed after this fix was released and the original issue fixed.

Could you open a new issue giving us more information about your proxy setup? I’m sure we’ll sort it up!