chai | benchmark suite of Collaborative Heterogeneous Applications | GPU library

You passed --presets=env and the error is trying to tell you that instead of that, it should be --presets=@babel/preset-env.

DISCLAIMER: First of all, the way I posted the question was without all of the code in all of the files because I thought it would clutter the post with endpoints and tests that weren't affecting mine. Now the question has another endpoint which is what was causing trouble: GET /listings/:listing_id.

Apparently in Express the order of the endpoint definition matters so what happened was that my test was trying to interpret GET /listings/ranking as if ranking was a listing_id only because the /:listing_id was defined before it. So it was returning 404 because no listing with the ID "ranking" existed.

to test locally you need to make use of mocks which can simulate having an oracle network. Because you're working locally, a Chainlink node doesn't know about your local blockchain, so you can't actually do proper VRF requests. Note you can try deploy a local Chainlink node and a local blockchain and have them talk, but it isn't fully supported yet so you may get mixed results. Anyway, as per the hardhat starter kit that you linked, you can set the defaultNetwork to be 'hardhat' in the hardhat.config.js file, then when you deploy and run the integration tests (yarn test-integration), it will use mocks to mock up the VRF node, and to test the requesting of a random number. See the test here, and the mock contracts and linktoken get deployed here

Something very important to point out is that you are currently trying to use a Firebase callable function, as shown by the function heading functions.https.onCall(() => {});. Since you want to work with requests and response codes, the correct type of function to use is an HTTP function. You would only need to change the heading in your index.js:

I was facing the same issue which is why I stumbled across this post.

My issue was I was using the wrong node version. I faced a similar issue after upgrading to Angular 13 but I was using node version v14.2.0.

I changed the node version to v14.15.0 and it worked.

nvm use v14.15.0

PS: NVM manages multiple nodejs versions.

The syntax is expect(something).to.match and not expect(something).should.match. See docs. Or, if you want to use should, you don't need expect, since the syntax for that is something.should.match.

The fix is therefore to change your code either as follows:

you could iterate data and and create tests and files dynamically, and attach them, including also all file related info for the server to parse:

I finally found the root cause! OpenSea expects a public property called name in order to display the proper Name of the Collection instead of a static label Unidentified contract.

I came across this while looking at their reference code (which depends on a now 3-year-old MultiToken-Contract implementation and needs all in all some downgrades of Node and other tools in order to get it build [a downgrade to Node 10 worked best for me today] ).

To resolve this issue update the "passport" lib version in your package.json: from "passport": "^0.5.2", to "passport": "^0.4.0", so it's same as used in @nestjs/passport@8.0.1.