Reference Transferwise Environment Variable directly without Destructuring #6441
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.
As pointed out by the discussion here, #6418 (comment) there seems to be some problems with Webpacks environment variable de-structuring; webpack/webpack#5392.
This PR corrects that. I did some search on a cleaner approach and although the official documentation doesn't seem to mention that there's an idea on this post; https://prateeksurana.me/blog/using-environment-variables-with-webpack/#accessing-environment-variables-via-webpack which is to use a separate file for the environment variables, and refer them from that file. We can employ this approach if there's no objection. 🤔
@znarf @Betree