feat: add support of http agents and proxy #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the possibility to provide a custom http agent on figma-js client instantiation.
This allows figma-js to be used in different environments (proxy,...)
The current version of figma-js can only be used with a direct internet connection.
In specific cases such as in a company environment (example: need a proxy to connect internet), figma-js does not work.
Allowing a client to change http_agent, https_agent, or/and proxy values of axios configuration enables developers to make clients that work in more environments, such as (but not limited to) using http_proxy environment if present to connect via proxy.
Figma-js interface is kept the same (new values are optional), so it is backward compatible.