search

walnuthq / op-scan

Lightweight transaction explorer for the OP Stack.
https://opscan.co
11 stars 21 forks source link

Build errors #72

Closed celochoi closed 2 weeks ago

celochoi commented 1 month ago

When performing pnpm build on the current main branch, the following error occurs.

./src/hooks/useSearch.ts
Error:
  x Expected '>', got 'ref'

It seems to have started occurring after this commit. Could you check it?

saimeunt commented 4 weeks ago

@celochoi You are right, it should be fixed by the latest commit now, thank you for pointing this out! I'm curious what's your use case for trying out op-scan, would you be open to share it with us? We're trying to reach essential/basic features parity with Etherscan/Blockscout and then we'll dive into op-stack related features (SuperchainERC20, ERC-7683) but most importantly we want to bring features that potential users are interested in!

ScottyDavies commented 2 weeks ago

@celochoi I am open to work on this

onlydustapp[bot] commented 2 weeks ago

Hey @ScottyDavies! Thanks for showing interest. We've created an application for you to contribute to opscan by walnut. Go check it out on OnlyDust!

devcollinss commented 2 weeks ago

Can I work on this please @celochoi , please I’d love to be given the opportunity to contribute here.

onlydustapp[bot] commented 2 weeks ago

Hey @devcollinss! Thanks for showing interest. We've created an application for you to contribute to opscan by walnut. Go check it out on OnlyDust!

celochoi commented 2 weeks ago

@saimeunt I apologize for the delayed response. I'm interested in setting up an OP Stack L2 chain, and I anticipate that implementing my own scanner would require substantial resources. Given that many chains using the OP Stack exist, I expected there would be open-source scanners available, and I have come across Op Scan during search. :)

celochoi commented 2 weeks ago

Since a scanner is essential for chain operation, I'm paying close attention to it. Thank you.

celochoi commented 2 weeks ago

It appears that this issue has been resolved in the latest main branch, so I will go ahead and close it.