<npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/react npm WARN peer react@"^17.0.2 || ^18.0.0-0" from [email protected] npm WARN node_modules/next npm WARN next@"12.3.0" from the root project npm WARN 12 more (react-dom, styled-jsx, use-sync-external-store, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer react@"^17.0.0" from [email protected] npm WARN node_modules/wagmi npm WARN wagmi@"^0.2.28" from @thirdweb-dev/[email protected] npm WARN node_modules/@thirdweb-dev/react npm WARN npm WARN Conflicting peer dependency: [email protected] npm WARN node_modules/react npm WARN peer react@"^17.0.0" from [email protected] npm WARN node_modules/wagmi npm WARN wagmi@"^0.2.28" from @thirdweb-dev/[email protected] npm WARN node_modules/@thirdweb-dev/react npm ERR! code ENOENT npm ERR! syscall spawn git npm ERR! path git npm ERR! errno -2 npm ERR! enoent An unknown git error occurred npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in:>

when the installation is done it shows an error and it is not added to the package.json

i have been looking for the best solution fix this start node.js reinstallation and others

I check and see here you only return contract address. My code:

let params = {
			name: name,
			symbol: symbol || "",
			fee_recipient: recipient || currentAddress,
			primary_sale_recipient: recipient || currentAddress,
			platform_fee_recipient: recipient || currentAddress,
			seller_fee_basis_points: fee || 0,
			platform_fee_basis_points: fee || 0,
			description: `hazbase:${currentProjectId}`
		}

contractId = await sdk.deployer.deployNFTCollection(params)
 contractId = await sdk.deployer.deployEditionDrop(params)
contractId = await sdk.deployer.deployNFTDrop(params)
contractId = await sdk.deployer.deployToken(params)

You code :

deployNFTCollection(metadata: NFTContractDeployMetadata): Promise<string>;

Issues:

When many of my users use gasless, I want to save the information for customers to pay through Openzeplin. I don't see this function returning txHash but returning address.

But I see other functions like MintToken, SendToken, ... that return txid, like below.

My code get txid :

switch (contractType) {
		case 'edition-drop':
			contract = sdk.getEditionDrop(currentContractId)
			return txid = await contract.createBatch(Array.isArray(data)? data: [data])
		case 'nft-collection':
			contract = sdk.getNFTCollection(currentContractId)
			return txid = await contract.mintBatch(Array.isArray(data)? data: [data])
		case 'nft-drop':
			contract = sdk.getNFTDrop(currentContractId)
			return txid = await contract.createBatch(Array.isArray(data)? data: [data])
		case 'token':
			contract = sdk.getToken(currentContractId)
			return txid = await contract.mintTo(params.mintto, params.amount)
		default:
			break;
	}

YouCode return txid:

mintBatch(metadata: NFTMetadataOrUri[]): Promise<TransactionResultWithId<NFTMetadataOwner>[]>;

Can you help me pay extra txID when deploying contract . Thanks!!!

Initializing a contract through the useContract hook almost always results in undefined.

index.js

import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App';
import reportWebVitals from './reportWebVitals';
import { ThirdwebProvider } from "@thirdweb-dev/react";

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
  <React.StrictMode>
    <ThirdwebProvider
    >
        <App />
    </ThirdwebProvider>
  </React.StrictMode>
);

reportWebVitals();

App.js

import Home from "./pages/Home";

function App() {
  return (
   <Home></Home>
  );
}

export default App;

Home.js

import React from 'react';
import { ConnectWallet, ChainId, useContract, useContractWrite } from "@thirdweb-dev/react";
import myABI from "./myABI.json";


function Home() {
    const { contract } = useContract("0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", myABI);

    console.log(contract);
    console.log(myABI);

    return (
        <>
            <ConnectWallet accentColor="#f213a4" colorMode="dark" />

            <h1>Thirdweb</h1>
        </>
    );
}

export default Home;

myABI.json

[{"constant":false,"inputs":[{"name":"newImplementation","type":"address"}],"name":"upgradeTo","outputs":[],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":false,"inputs":[{"name":"newImplementation","type":"address"},{"name":"data","type":"bytes"}],"name":"upgradeToAndCall","outputs":[],"payable":true,"stateMutability":"payable","type":"function"},{"constant":true,"inputs":[],"name":"implementation","outputs":[{"name":"","type":"address"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":false,"inputs":[{"name":"newAdmin","type":"address"}],"name":"changeAdmin","outputs":[],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":true,"inputs":[],"name":"admin","outputs":[{"name":"","type":"address"}],"payable":false,"stateMutability":"view","type":"function"},{"inputs":[{"name":"_implementation","type":"address"}],"payable":false,"stateMutability":"nonpayable","type":"constructor"},{"payable":true,"stateMutability":"payable","type":"fallback"},{"anonymous":false,"inputs":[{"indexed":false,"name":"previousAdmin","type":"address"},{"indexed":false,"name":"newAdmin","type":"address"}],"name":"AdminChanged","type":"event"},{"anonymous":false,"inputs":[{"indexed":false,"name":"implementation","type":"address"}],"name":"Upgraded","type":"event"}]

I am connected using the ConnectWallet button, and the network is the same as the one the contract is on (mainnet, the contract is the address of the USDC token).

Tried it with different ABIs and contract addresses, as well as without any ABI, just the address. Why does this happen? Does the hook work ONLY for contracts deployed using the Thirdweb Dashboard, or what's the case here?

Background

Working with BigNumber variables requires importing ethers and using ethers.utils.formatEther and parseEther functions which is not very discoverable through our SDK unless you are already familiar with the ethers dependency.

It would be great to expose convenience functions that expose these directly from our SDK package rather than ethers.

Goal

[] Add toEther function

• Users can import toEther from the @thirdweb-dev/sdk package and convert a number from wei to formatted value. Use the ethers.utils.formatEther functionality under the hood.

[] Add toWei function

• Same as above, except use parseEther under the hood.

When i deploy contract with network GEORI and success. Then I use method const list = await sdk.getContractList(currentAddress) to get all List contract .

I get the result that no contracts can be found deployed using gasless and using a regular wallet is successful.

I tested with RINKEBY network, it was successful and no error Can you help me to test GEORI network and mainnet networks.

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• Updated dependencies [557429b, 9eaa21d]:
  • @thirdweb-dev/[email protected]

@thirdweb-dev/[email protected]

Patch Changes

• #463 557429b Thanks @joaquim-verges! - PackVRF contract

• #311 9eaa21d Thanks @joaquim-verges! - Update to v3.3.0 of contracts package

• #311 9eaa21d Thanks @joaquim-verges! - Update to 3.1.10 of contracts package

@thirdweb-dev/[email protected]

Patch Changes

• #463 557429b Thanks @joaquim-verges! - PackVRF integration

• #311 9eaa21d Thanks @joaquim-verges! - Add support for multi chain registry

• Updated dependencies [557429b, 9eaa21d, 9eaa21d]:

  • @thirdweb-dev/[email protected]

@thirdweb-dev/[email protected]

Patch Changes

• Updated dependencies [557429b, 9eaa21d]:
  • @thirdweb-dev/[email protected]

@thirdweb-dev/[email protected]

@thirdweb-dev/[email protected]

Bumps json5 from 1.0.1 to 1.0.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I have two different public addresses for the following methods

import { EthNetworkConfiguration, Magic } from 'magic-sdk';

const magic = new Magic(process.env.NEXT_PUBLIC_MAGIC_API_KEY, {
  network: process.env.NEXT_PUBLIC_CHAIN_KEY as EthNetworkConfiguration,
});
await magic.auth.loginWithMagicLink({ email:  '[email protected]'  });

const provider = new ethers.providers.Web3Provider(magic.rpcProvider);
const magicSigner = provider.getSigner();
const address = await magicSigner.getAddress();
console.log(address)

and

import { useMagic, useAddress } from '@thirdweb-dev/react/evm/connectors/magic';
const connectWithMagic = useMagic();
const address = useAddress()

await connectWithMagic({ email: '[email protected]' })
console.log(address)

Here is the Sandbox to reproduce the issue: https://github.com/rekolt/magic-link

If I use the same email, I should have one single address, correct? Why do I have two different?

Issue

When sending a blank GET request to /api/auth/login using @thirdweb/auth in Next.js (and Express.js as well) the whole server crashes because of an unexpected token in this line of code.

This might be a vulnerability because this is a way to crash the whole backend with one single request.

Also to mention that the atob method used here is deprecated.

const payload = JSON.parse(atob(req.query.payload as string)) as LoginPayload;

The error

error - node_modules/@thirdweb-dev/auth/next/evm/dist/thirdweb-dev-auth-next-evm.esm.js (20:0) @ handler$2
error - SyntaxError: Unexpected token º in JSON at position 0
    at JSON.parse (<anonymous>)

Possible solutions

1. Replace the deprecated atob method with the modern Buffer.from method.
2. Handle the case where the req.query.payload is null or undefined.
3. Catch server errors in the whole route handler.