Type of Change
Summary
To maximize the potential and viability of wcc across as many runtimes as possible, an effort should be undertaken to ensure support across "standards" based serverless and edge runtime environments. Serverless environments are a little more forgiving, but edge functions typically cannot not use things like Node's fs or CommonJS. However, they do (plan to) standardize on Web APIs like fetch, Request and Response.
Details
Basically need to evaluate and allow wcc to be usable outside of just NodeJS. That will mean validating our dependencies for their module system, and any usage of Node specific APIs like fs. Perhaps this may require a pre-bundle if there is an expectation of ESM only as well, but we will have to see.
I think it would be great to reach
- Lambda@Edge
- Netlify Edge Functions
- Cloudflare Workers
- Vercel
Type of Change
Summary
To maximize the potential and viability of
wccacross as many runtimes as possible, an effort should be undertaken to ensure support across "standards" based serverless and edge runtime environments. Serverless environments are a little more forgiving, but edge functions typically cannot not use things like Node'sfsor CommonJS. However, they do (plan to) standardize on Web APIs likefetch,RequestandResponse.Details
Basically need to evaluate and allow
wccto be usable outside of just NodeJS. That will mean validating our dependencies for their module system, and any usage of Node specific APIs likefs. Perhaps this may require a pre-bundle if there is an expectation of ESM only as well, but we will have to see.I think it would be great to reach