@matter/examples 0.13.0-alpha.0-20250307-ebf84a05a → 0.13.0-alpha.0-20250318-c1aa38b08

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -52,14 +52,6 @@ Some command line parameters, for example those used to set the level of logging
52
52
  * `--mdns-networkinterface=...` or environment variable `MATTER_MDNS_NETWORKINTERFACE` or `environment.vars.set('mdns.networkInterface', "...")` allows to limit the DNS announcements and scanning to one network interface. By default, all available interfaces are used.
53
53
  Additionally, all command line parameters now require to start with two dashes!
54
54
 
55
- ### Common CLI parameter for all examples
56
- The following CLI parameters are the same for all examples:
57
-
58
- * -clearstorage: the storage location will be reset on start of the process. The storage location is set via parameter "-store" (see concrete examples below)
59
- * -loglevel: the log level to use (default: debug, possible values: fatal, error, warn, info, debug)
60
- * -logformat: the log format to use (default: ansi (if executed in a shell/tty), else plain, possible values: ansi, plain, html)
61
-
62
-
63
55
  ## Development on basis of the examples
64
56
 
65
57
  The code of the examples is written so that you can use them as basis for your own scripts also outside of this library in your own package. If you import from `@matter/main` then matter.js loads platform extensions such as those for node.js automatically. If you import directly from our other packages then you should add a dependency on `@matter/nodejs`. The examples use `@matter/main` imports to ease adoption.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@matter/examples",
3
- "version": "0.13.0-alpha.0-20250307-ebf84a05a",
3
+ "version": "0.13.0-alpha.0-20250318-c1aa38b08",
4
4
  "description": "Matter.js examples and reference implementations",
5
5
  "keywords": [
6
6
  "iot",
@@ -52,13 +52,13 @@
52
52
  "matter-controller": "dist/esm/controller/ControllerNode.js"
53
53
  },
54
54
  "dependencies": {
55
- "@matter/main": "0.13.0-alpha.0-20250307-ebf84a05a",
56
- "@matter/nodejs": "0.13.0-alpha.0-20250307-ebf84a05a",
57
- "@matter/tools": "0.13.0-alpha.0-20250307-ebf84a05a",
55
+ "@matter/main": "0.13.0-alpha.0-20250318-c1aa38b08",
56
+ "@matter/nodejs": "0.13.0-alpha.0-20250318-c1aa38b08",
57
+ "@matter/tools": "0.13.0-alpha.0-20250318-c1aa38b08",
58
58
  "esbuild": "^0.25.0"
59
59
  },
60
60
  "optionalDependencies": {
61
- "@matter/nodejs-ble": "0.13.0-alpha.0-20250307-ebf84a05a"
61
+ "@matter/nodejs-ble": "0.13.0-alpha.0-20250318-c1aa38b08"
62
62
  },
63
63
  "engines": {
64
64
  "node": ">=18.0.0"
@@ -28,7 +28,7 @@ This will commission a MatterServer device (for debugging/capability showing pur
28
28
  The following parameters are available and used to initially commission a device (they can be omitted after this):
29
29
  * --fabriclabel: the fabric label to use for commissioning (default: "matter.js Controller")
30
30
  * If the IP and Port of the device is known (should be only the case in testing cases) you can use the following parameters:
31
- * --ip: the IP address of the device to commission (can be used but discovery via pairingcode or discriminator or also just pin (passode) is most likely better)
31
+ * --ip: the IP address of the device to commission (can be used but discovery via pairingcode or discriminator or also just pin (passcode) is most likely better)
32
32
  * --port the port of the device to commission (default: 5540)
33
33
  * Device identification options:
34
34
  * --pairingcode: code to use for pairing (-longDiscriminator and -pin will be ignored) - usually the code below the QR Code on the device or displayed in the app!