The current implementation has the remoteEntry.js URL hardcoded, which poses challenges for local testing and integration with MetaMask StarkNet Snap. To address this issue, we propose introducing an environment variable to dynamically handle the URL. This enhancement will improve the flexibility and ease of testing different environments.
We suggest adding a new environment variable named VITE_MM_FED_URL. This variable will allow developers to specify the remoteEntry.js URL during local development. If the variable is not set, the system will default to the original hardcoded URL, ensuring backward compatibility.
khanti42
commented
5 months ago
The current implementation has the
remoteEntry.jsURL hardcoded, which poses challenges for local testing and integration with MetaMask StarkNet Snap. To address this issue, we propose introducing an environment variable to dynamically handle the URL. This enhancement will improve the flexibility and ease of testing different environments.We suggest adding a new environment variable named
VITE_MM_FED_URL. This variable will allow developers to specify theremoteEntry.jsURL during local development. If the variable is not set, the system will default to the original hardcoded URL, ensuring backward compatibility.file concerned :
packages/core/src/wallet/metamaskBridge.ts