Necessary changes to get past: "Required dependency Crypto is not available"

[dpsthree]

I've been looking around and I'm struggling to figure out what I need to do to get the latest version of the controller working. I updated and now I see the error mentioned in the title. What am I missing?

I've tried Node 20.18.1, 22.12.0, and 24.4.1 all with the same results.
I'm using packages:
@matter/main: 0.15.3
@matter/node: 0.15.3
@matter/nodejs-ble: 0.15.3
@project-chip/matter.js: 0.15.3

This happens in my project as well as the controller example in the repo. My project setup is somewhat involved using NX and Nest. But to test the example I am just using: npx tsx matter-example.ts. Both setups produce the same error. What is strange is that if I leave out the environment when instantiating a ComissioningController the Crypto error disappears. So instead of

const environment = Environment.default;
this.controller = new CommissioningController({
      environment: {
        environment,
        id: 'node-server',
      },
      adminFabricLabel,
    });

I just instantiate with:

this.controller = new CommissioningController({
  adminFabricLabel,
});

The Crypto error is replaced with:
[implementation] Initialization not done. Add the controller to the MatterServer first.

[lauckhart]

Matter.js should configure crypto automatically for your runtime if possible. If you're on node.js, what version? How are you launching matter.js code?

[dpsthree]

Updated original post with more details

[dpsthree]

OK, I ran the example script as it sits in the repository and it works. I had copied the file to a different location for ease of access. So there is something different about the example repository and a standalone execution. Will continue to investigate.

[lauckhart]

OK, on node the default environment should contain NodeJsCrypto. The node environment registers here: https://github.com/matter-js/matter/blob/main/packages%2Fnodejs%2Fsrc%2Fenvironment%2Fregister.ts#L10

That registration should happen automatically if you import via @matter/main as documented here: https://github.com/matter-js/matter/blob/main/packages/nodejs/README.md

I'm not sure why that isn't working for you... I wouldn't expect tsx to cause problems but maybe it's doing something funky with imports. If you can figure out what the issue is let us know so we can fix or document. Or if you want to push the broken code somewhere I can poke at it.

[dpsthree]

I figured it out, user error. Thanks for being a sounding board.

[dpsthree]

OK, facepalm moment. My packages were actually:

@matter/main: ^0.15.3
@matter/node: ^0.15.3
@matter/nodejs-ble: ^0.15.3
@project-chip/matter.js: ^0.15.3

It's amazing the time that '^' and '~' can waste, even for people who should know better :D
Locking the version, deleting node_modules and package-lock fixed the issue.

[Apollon77]

Cool you solved it, I also have a question/feedback:
For what you need the @matter/node package? in fact all relevant exports should be also available using the main package.

Additionally our best practice is to use hard defined depnendecy definitions, so do not use ^ or ~ at all and always manually make sure the versions match exactly.