did you follow the steps outlined in the sub-section Adding pre-developed frontend code?
you need to make some changes to dfx.json
, add various frontend related files (index.html
, …), then run npm install
and then run dfx deploy
again.
did you follow the steps outlined in the sub-section Adding pre-developed frontend code?
you need to make some changes to dfx.json
, add various frontend related files (index.html
, …), then run npm install
and then run dfx deploy
again.
In 1.4 Acquiring and using cycles, I get an error in submitting the cycles-faucet survey. It just said something like “error, please try again.” I did fill in all the mandatory fields. What might cause submission to fail?
Hi @kevinmcfarlane , could you please report this error in the Discord server where you are submitting the survey, as the team there would be best suited to help troubleshoot errors with it. Also, perhaps @cryptoschindler might have some insight. Thanks!
I’ve done that as well (yesterday) but not had a response as yet. Btw, can the rest of the developer journey, or most of it, be completed in the local environment?
Yes, deploying to the mainnet and using cycles is optional for most of the journey.
Did you request cycles before with your GitHub or Discord account?
I did work through some tutorials as they were about 18 months ago. I can’t recall whether they involved the mainnet but if so, I may well have done.
But, as Jessie says, I can work through most of the dev journey in the local environment and then buy cycles if and when I start getting serious.
I’m stuck on Section 2.5 Unit, integration, and end-to-end testing.
Error: Failed to load url @dfinity/agent (resolved id: @dfinity/agent) in /home/kevin/developer_journey/e2e_tests/src/tests/actor.js. Does the file exist?
In the file e2e_tests_backend.test.ts I get
“Cannot find module ‘@dfinity/agent’ or its corresponding type declarations.”
My package.json currently looks like this:
{
“name”: “bun-test”,
“version”: “1.0.0”,
“description”: “”,
“main”: “index.js”,
“scripts”: {
“test”: “vitest”,
“ci”: “vitest run”,
“preci”: “dfx stop; dfx start --background --clean; dfx deploy; dfx generate”
},
“keywords”: ,
“author”: “”,
“license”: “ISC”,
“dependencies”: {
“@dfinity/agent”: “^2.1.3”,
“@dfinity/identity”: “^2.1.3”,
“@dfinity/principal”: “^2.1.3”,
“bip39”: “^3.0.4”,
“hdkey”: “^2.0.1”,
“isomorphic-fetch”: “^3.0.0”
},
“devDependencies”: {
“vitest”: “^2.1.5”
}
}
Let me know if there’s anything else you need to examine.
Before I forget, I just wanted to note that the API endpoint used in this tutorial is no longer working. About ten days ago, I started working on an alternative, exploring different services that provide a similar endpoint for free. I haven’t looked at it since, so I don’t really remember the current state of the project, but if Jessie (or anyone else) needs inspiration, it’s here.
Thanks @552020 , this series is currently being revised to use examples from the ICP Ninja web IDE, so the HTTPS outcalls example will be updated soon.