claudebarde / taquito-pinata-tezos-nft Goto Github PK

Hi @claudebarde , thanks for the great article! I ran into two small issues setting this up locally.

I'm not able to submit a PR, but in case anyone comes across this, these are the changes I needed to make:

In backend/src/index.ts:

-  const PinataKeys = require("./PinataKeys");
+  const PinataKeys = require("./PinataKeys").default;

In frontend/src/App.svelte:

-          data.status === 200 &&
+          data.status === true &&

Frontend built, backend no:

12 pinata = pinataSDK(process.env.PINATA_API_KEY, process.env.PINATA_SECRET_KEY);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/index.ts:15:12 - error TS2348: Value of type 'typeof PinataClient' is not callable. Did you mean to include 'new'?

15 pinata = pinataSDK(PinataKeys.apiKey, PinataKeys.apiSecret);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: src/index.ts:12

npm ERR! code 2
npm ERR! path /Users/James/taquito-pinata-tezos-nft/backend
npm ERR! command failed
npm ERR! command sh -c tsc

Hi @claudebarde, thanks for the excellent tutorial. I think I almost have it working however Florencenet is deprecated as of August 6, 2021

I assume changing the references to Hangzhounet will fix this however I'm unable to submit a PR

Cheers!

Lots of errors. Is this project up to date?

Hi Claude!

Assuming this is the tutorial:
https://wiki.tezos.com/build/create-a-tezos-token/nft

It looks like the tutorial is written for production but there's no instructions on setting up Heroku or any path/filenames for the code snippets.

Could you please add some steps to set up Heroku with the url please? Or how to get up and running on localhost?

I tried running npm install on macbook in frontend directory but got:

npm ERR! path /Users/leotreasure/taquito-pinata-tezos-nft/frontend/node_modules/node-sass

Not certain what the problem is, but it's connected to CORs not allowing Ithacanet to connect.

Probably related to ithacanet returning 404 on request