web3-react VS emotion

What are we building? Using hardhat, we will deploy a smart contract to the goerli testnet, this contract creates a token and also is able to send these tokens to other address. For the frontend we will use react, for the interaction with the smart contract we will use Metamask and web3-react. Finally, for the analytics of our dapp we will be using sumer.

web3-react

About the stack: - Typescript - Nextjs - TailwindCSS - Styled Components - Emotion - Twin.Macro (combining Styled Components with TailwindCSS) - NextI18Next integrated (wrong translationkeys result in compilation errors) - Web3React - Ethers - Redux Toolkit + Redux Observables (with hydration example) - Ramda among others

Make sure you have some understanding of HTML/CSS. Check out Automate The Boring Stuff to learn some Python and then check out Real Python to learn some Django for your backend stuff. From there you're going to want to learn Solidity and for that I suggest checking out Crypto Zombies. Then you can learn a JavaScript frontend framework like React which has cool packages for web3 like web3-react. I'm on mobile and probably butchered this but it should give you some idea.

125.6a8cb8bf74e9194d3ec0.js - nft_web_store_client - "Unsupported chain id" - cached here: https://github.com/NoahZinsmeister/web3-react - possible source code: https://webcache.googleusercontent.com/search?q=cache:Yk5w0-pnrWsJ:https://beta.quod.ai/github/NoahZinsmeister/web3-react/simple-answer/210/Where-do-we-react-manager-for-web3+&cd=1&hl=en&ct=clnk&gl=us - Code likely written by https://noahzinsmeister.com/ - "Web3ReactUpdate" - "The provider doesn't support subscriptions" - "Couldn't decrypt accounts. Password wrong?" - ipfs

Web3-React, a connecting framework for React and Ethereum, can help us with job 1 & 2. Web3-React is an open source framework developed Uniswap engineering Lead Noah Zinsmeister. (We will focus on job 1.)

documents https://github.com/NoahZinsmeister/web3-react/tree/v6/docs

Please note that @web3-react changes a little. @web3-react/injected-connector and @web3-react/walletconnect-connector are used here. But maybe we should update with @web3-react. Please find: https://github.com/NoahZinsmeister/web3-react

emotion [ https://emotion.sh ]

dang, I never thought about this implication, and I googled the emotionjs repo there's a currently-active open issue regarding this https://github.com/emotion-js/emotion/issues/2928

Over my years of working with React, I’ve loved using CSS-in-JS libraries like Emotion and Styled-components. However, their inherent performance overhead from injecting CSS at runtime and their incompatibility with the latest Next.js features such as App Router and React Server Components (RSC) have always been a nagging issue for me.

An early difficulty I encountered was using UI component libraries like Mantine and Material UI in the new architecture. After looking through some GitHub issues, the culprit is Emotion, a package many component libraries rely on that does not support server rendering.

In general I recommend using styled-components or emotion. These directly attach CSS to your components in a scoped way so that your CSS files aren’t stepping on each other’s toes all the time and make sure styling is colocated with the component.

I ran into this problem as well. The root cause as I understand it is emotion: https://github.com/emotion-js/emotion/issues/2928

While integrating component libraries, they may not give you full control over the order in which styles are inserted. (Example issue).

Vanilla Extract (CSS Framework) (Alternative: Emotion)