feat: add HTTPS support for Edge Functions in Netlify Dev

[eduardoboucas]

Summary

Fixes an issue where origin requests in Edge Functions will fail when running Netlify Dev with HTTPS enabled.

Builds on top of https://github.com/netlify/edge-functions-bootstrap/pull/30 and netlify/edge-bundler#7 (the tests will fail until both of these are merged and released).

Closes https://github.com/netlify/pillar-runtime/issues/323.

[github-actions]

📊 Benchmark results

Comparing with 6695113

Package size: 274 MB

⬆️ 0.17% increase vs. 6695113

^  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB  380 MB         
│   ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐    ┌──┐          
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |          
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |          
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |          
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |          
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |   274 MB 
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    ┌──┐  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
│   |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |  |    |▒▒|  
└───┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴────┴──┴──>
    T-12    T-11    T-10    T-9     T-8     T-7     T-6     T-5     T-4     T-3     T-2     T-1      T    

Legend

• T-30 (6695113): 273 MB
• T-29 (79cab6c): 273 MB
• T-28 (f35b14c): 273 MB
• T-27 (2c58896): 273 MB
• T-26 (8945228): 273 MB
• T-25 (9998550): 273 MB
• T-24 (d9bb192): 273 MB
• T-23 (129216e): 273 MB
• T-22 (59c3670): 273 MB
• T-21 (fbd4510): 380 MB
• T-20 (47181a4): 380 MB
• T-19 (d8bc64e): 380 MB
• T-18 (02c8c8a): 380 MB
• T-17 (15d351e): 380 MB
• T-16 (647ad4d): 380 MB
• T-15 (c285dbc): 380 MB
• T-14 (4ad0b45): 380 MB
• T-13 (a668861): 380 MB
• T-12 (1cb5a91): 380 MB
• T-11 (15f34db): 380 MB
• T-10 (3725113): 380 MB
• T-9 (62e64c4): 380 MB
• T-8 (3840cc4): 380 MB
• T-7 (0f69bb5): 380 MB
• T-6 (ccd26a5): 380 MB
• T-5 (6866549): 380 MB
• T-4 (6a16b6e): 380 MB
• T-3 (1fd0c2c): 380 MB
• T-2 (84fa9f6): 380 MB
• T-1 (e4f6ef0): 380 MB
• T (current commit): 274 MB

[Skn0tt]

AFAICT, this will require every developer cloning this repository to run npm run certs as part of setting up their development environment. Could we use something like https://www.npmjs.com/package/openssl-nodejs (or execa) to generate the certificates as part of the test run? Or is that too resource-intensive?

[eduardoboucas]

AFAICT, this will require every developer cloning this repository to run npm run certs as part of setting up their development environment. Could we use something like https://www.npmjs.com/package/openssl-nodejs (or execa) to generate the certificates as part of the test run? Or is that too resource-intensive?

@Skn0tt I've added certs to the test:dev script in c43991f. I think that should cover it?

[Skn0tt]

Yes, that's good 👍