Opensea clone. Module not found

Moralis General
#1

Hey Guys
I’m having a issue with the Opensea clone. I have checked the file oath for this error and I’ve
checked my SearchCollections.jsx and I have imported it correctly. Can someone help me please?
Cheers

Screenshot 2022-07-21 150222
Screenshot 2022-07-21 1502221907×502 59.7 KB

SearchCollections.jsx

import { Select } from "antd";

import { useMoralisDapp } from "providers/MoralisDappProvider/MoralisDappProvider";

import { getCollectionsByChain } from "helpers/collections";

function SearchCollections({ setInputValue }) {

  const { Option } = Select;

  const { chainId } = useMoralisDapp();

  const NFTCollections = getCollectionsByChain(chainId);

  function onChange(value) {

    setInputValue(value);

  }

  return (

    <>

      <Select

        showSearch

        style={{ width: "1000px", marginLeft: "20px" }}

        placeholder="Find a Collection"

        optionFilterProp="children"

        onChange={onChange}

      >

        {NFTCollections &&

          NFTCollections.map((collection, i) => (

            <Option value={collection.addrs} key={i}>

              {collection.name}

            </Option>

          ))}

      </Select>

    </>

  );

}

export default SearchCollections;
#2

Do you have providers folder under src?
If yes, maybe try adding the ../

import { useMoralisDapp } from "../providers/MoralisDappProvider/MoralisDappProvider";
#3

Hi John
Thank you.
I was able to get past this and I’m trying to figure out how to fix this 400 post error. They only showed up this morning. I did not have these 400 errors last night when logged off for the night.
I do now have [HMR] Waiting for update signal from WDS... at the top of my console and was wondering if this is the cause?
I’m enjoying React alot :slight_smile:
Cheers

Screenshot for Joh on friday
Screenshot for Joh on friday445×758 38.1 KB

#4

You can click into the 400 links to see the error (and click the 400 error again) - if for some of the errors you get a payload like address: "explore", you can ignore them, it’s an issue with the boilerplate to begin with.

For the key prop warning, you can ignore that for now. If you want to fix it, you can read about it here.

1 Like
#5

Thank you Glad.
Much appreciated

#6
#7