So I’ve been trying to run queries from node.js, and wanted to document the process, if anyone is interested. I’m also hoping some of the workarounds that I found can be properly patched so we can use services like heroku without having to jump trough hoops. :~/work/dfinity/node_test_2$ node -v v10…

to support the latest agent release 0.21.3 that uses noble it seems like you only need to pass in the secret key, therefore adapt decode in @ZenVoich script to the following function decode(rawKey: string) { const buf: Buffer = pemfile.decode(rawKey); if (rawKey.includes('EC PRIVATE KEY')) { if…

What am I missing here? I used this pattern in my node.js script, and the identity actually works fine. The problem is that when I try to include my actor from /src/declaration/project_name/project_name.js or /src/declaration/project_name/index.js I get the dreaded: SyntaxError: Unexpected token ‘…

[image] skilesare: But this is really annoying to do every time. If you are using NodeJS LTS or more recent versions you can use script module files .mjs. What I do is adding a postbuild script in package.json that automatically copy the .did.js files to .did.mjs files. Then in myscript.mjs …

Just to confirm… I want to use my default dfx identity to authenticate with my canister using the @dfinity/agent library in node… Ideally using the PEM file in ~/.config/dfx/identity/default/identity.pem. I’m guessing from this thread that this is not possible right now? (I need to create a new ide…

I think you can use Key Smith to produce a back up phrase for your default identity. Just run the help for key Smith and you’ll see a number of options.

If I do this I have to convert all of my other require statements to import statements correct? I feel like I tried this but one of my existing packages demanded that I use require or something like that. I’ll give this a try and report back.

[image] skilesare: If I do this I have to convert all of my other require statements to import statements correct? Yes probably, a bit a pity but at least a one time change. Let me know if it works out :crossed_fingers:

Thanks to everyone above for the great commentary, really was nice to follow as I started troubleshooting not being able to load in my existing dfx principal via agent-js (I received the same different dfx and node principals as everyone else). Since it did take me a bit of time to get through it a…

So there’s no way to just pass in a path to a PEM file and get an identity that can be used in @dfinity/agent? It used to be the case that I could just pass in JSON object and all of this worked, that was last Summer. What happened?

a JSON object has always worked and still does work. The complicated flow is specifically for deriving an identical principal across dfx, quill, and agent-js

Do you know where the documentation is on what the JSON object should look like? I keep getting errors with it

Using @dfinity/agent in node.js

Developers

peterparker April 19, 2022, 1:47pm 49

Yes probably, a bit a pity but at least a one time change. Let me know if it works out

Topic		Replies	Views
How to use my local private keys in agent-js? JavaScript	4	2214	June 8, 2022
Fail to verify delegation certificate Developers	9	1236	March 14, 2022
Generated declarations in Node.js environment break Developers	28	2343	September 1, 2022
Where actually is the dfx idendity pem file? Developers	15	2758	February 26, 2022
How login manually in AuthClient using a generated identity for testing? Developers	7	1316	April 1, 2024

Using @dfinity/agent in node.js

Related topics