feat: resolve external APIs in the local build #211
Conversation
jcbsfilho
requested review from
jotanarciso,
MagnunAVFAzion,
enicio and
tiagokrebs
as code owners
|
I believe the polyfill should be in #env/polyfills. That is, this is an environment-adapted polyfill (#env), like fetchPolyfill, and should not appear in the final build artifacts. What do you think? |
I agree, let's move the external polyfills to the #env/polyfills path. |
[skip ci] ## [2.3.0-stage.1](v2.2.0...v2.3.0-stage.1) (2024-01-17) ### Features * added building with external api to local runtime ([52bcd13](52bcd13)) * adding partial implementation of async_hooks to local dev ([3665359](3665359)) * resolve external APIs in the local build ([#211](#211)) ([b265ed6](b265ed6))
|
🎉 This PR is included in version 2.3.0-stage.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
[skip ci] ## [2.3.0](v2.2.0...v2.3.0) (2024-01-22) ### Features * added building with external api to local runtime ([52bcd13](52bcd13)) * adding partial implementation of async_hooks to local dev ([3665359](3665359)) * resolve external APIs in the local build ([#211](#211)) ([b265ed6](b265ed6)) ### Bug Fixes * angular deliver preset ([#215](#215)) ([5bb2d77](5bb2d77)) * angular preset (deliver) ([f8c12b6](f8c12b6)) * remove versionid ([482fb35](482fb35)) * remove versionid ([#210](#210)) ([e78ea1e](e78ea1e))
|
🎉 This PR is included in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Goal:
On the local Vulcan server, resolve external APIs with polyfill.
And in the production build, the APIs will be marked as external.