Coming out of #1008 , Greenwood now has support for the following serverless hosting providers
1128
1139
With additional support coming soon for
1142
1143
Most of these platforms also support edge runtimes, so for these and upcoming adapter plugins, so we will want to look into adding Edge support as well. Something to keep in mind though is reproducing the "edge" runtime locally, since there will be geographic and custom context only available at runtime on the hosting platform.
Details
Based on reading done so far, I think there will likely just need to be an option to opt-in per file (or maybe a top level project wide config?) to determine if something should run at the edge or not, e.g.
I'm thinking this may need / want to be a post 1.x feature? Not sure which is more important, more adapters, or deeper integration with current adapters? 🤔
Type of Change
Feature
Summary
Coming out of #1008 , Greenwood now has support for the following serverless hosting providers
1128
1139
With additional support coming soon for
1142
1143
Most of these platforms also support edge runtimes, so for these and upcoming adapter plugins, so we will want to look into adding Edge support as well. Something to keep in mind though is reproducing the "edge" runtime locally, since there will be geographic and custom context only available at runtime on the hosting platform.
Details
Based on reading done so far, I think there will likely just need to be an option to opt-in per file (or maybe a top level project wide config?) to determine if something should run at the edge or not, e.g.
Integrating with local hosting platform CLIs would probably be super helpful here.