Daniel Farina

Confused about this. I had the exact same issue as @BlackConure and it adding ``` import store from '../renderer/store' ``` as mentioned by @Stormtv to the src/main/index.js fixed the issue...

This is something I'm currently exploring. Ideally we would do something like: ```js { rpc: process.env.NEXT_PUBLIC_OSMOSIS_RPC, rest: process.env.NEXT_PUBLIC_OSMOSIS_REST, chainId: process.env.NEXT_PUBLIC_OSMOSIS_CHAIN_ID, chainName: process.env.NEXT_PUBLIC_OSMOSIS_CHAIN_NAME, bip44: { coinType: 118, }, ``` However nextjs...

well, I think out setup is not just simply testnet vs mainnet, it could be a number of different environments. The NEXT_PUBLIC_IS_TESTNET should be kept in a .env file as...

> How would this apply to configuration on non-Osmosis chains? Like for Axelar? Which has testnet IBC connections. This is something that does not work on v12 currently or any...

I added env variables for Axelar so that we can configure the application to work with Axelar's testnet. - Added Axelar variables - Remove IS_TESTNET from `packages/web/config/chain-infos.ts` https://github.com/osmosis-labs/osmosis-frontend/pull/812/commits/ea451e1a3008d9a65c38279c8f235c624e980656 I also...

@niccoloraspa After having a good conversation with @jonator, we have decided to use a simpler approach and safer that unblocks devops automation. [NEW PR HERE ](https://github.com/osmosis-labs/osmosis-frontend/pull/824) @jonator I created a...

> Are the environment variables used at build time or runtime? I believe at build time but maybe @jonator can confirm. On dev, they don't get applied unless I stop...

This is ready ser @jonator @niccoloraspa Ready to test on stage.

> Please resolve conflicts @daniel-farina Conflicts fixed.

A good practice to get familiar with GrapeJS would be to attempt to duplicate the blocks manager and create your own. You can accomplish that by editing the files below....