question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DEPRECATED: Please use providerUtils.standardizeOrThrow() instead

See original GitHub issue

I ran into some issues while following the official documentation examples. Spent nearly a week trying to solve it, but found that it wasn’t something I could solve.

node -v 
v16.14.0

npm -v
8.1.2

package.json

{
  "name": "opensea-sdk",
  "version": "1.0.0",
  "description": "test",
  "scripts": {},
  "dependencies": {
    "opensea-js": "^3.0.4",
    "web3": "^1.7.3"
  },
  "type": "module"
}
// app.js

import Web3 from 'web3'
import { OpenSeaPort, Network } from 'opensea-js'

// This example provider won't let you make transactions, only read-only calls:
const provider = new Web3.providers.HttpProvider('https://mainnet.infura.io')

const seaport = new OpenSeaPort(provider, {
  networkName: Network.Main,
  apiKey: ''
})

The above code can restore my problem。 Looking for help here, I hope the official can pay attention to this problem and keep the project in a usable state.

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:6
  • Comments:15

github_iconTop GitHub Comments

3reactions
JorgeFPastorcommented, May 11, 2022

I am using web3 v1.7.3

this is from my package.json:

  "dependencies": {
    "opensea-js": "^2.0.2",
    "web3": "^1.7.3"
  }
2reactions
jerryfanecommented, Jun 6, 2022

This is a duplicate ticket, please follow this ticket for the latest updates on this issue to avoid confusion. I will go ahead and close.

#471

I’m facing the same issue and I don’t see how it is a duplicated issue. I already tried to install opensea-js both with npm and yarn, no luck.

Read more comments on GitHub >

github_iconTop Results From Across the Web

OpenSea Error - Please use providerUtils.standardizeOrThrow()
I'm currently on node v16.14.2. How can I resolve this issue? I appreciate the help! const Web3 = require("web3"); ...
Read more >
ProjectOpenSea - Bountysource
I am trying to use this library with Polygon and Matic but I see it is not really supported. Would at least like...
Read more >
Deprecated APIs | Node.js v19.3.0 Documentation
The Server.connections property was deprecated in Node.js v0.9.7 and has been removed. Please use the Server.getConnections() method instead.
Read more >
Deprecated and obsolete features - JavaScript - MDN Web Docs
This page lists features of JavaScript that are deprecated (that is, ... Use for...of instead. let blocks and let expressions are obsolete.
Read more >
Web3.modules - Web3.js - Read the Docs
WebsocketProvider('ws://localhost:8546')); // Using the IPC provider in ... Object - HttpProvider : The HTTP provider is deprecated, as it won't work for ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found