.toStrictEqual(expect.objectContaining(...)) can be replaced by .toMatchObject(...)

[sounisi5011]

The test code in this repository uses many of the following codes:

npm-packages/packages/check-pid-file/tests/index.ts

Lines 92 to 94 in 2a5ca2d

	.toStrictEqual(expect.objectContaining({
	code: 'ENOENT',
	}));

npm-packages/packages/cli/run-if-supported/tests/cli.mts

Lines 179 to 182 in 2a5ca2d

	.rejects.toStrictEqual(expect.objectContaining({
	stdout: '',
	stderr: expect.stringMatching(/^Error: "package.json" file is not found(?:$|\n)/),
	}));

npm-packages/packages/stream-transform-from/tests/public-api.ts

Lines 687 to 689 in 2a5ca2d

	await expect(errorPromise).resolves.toStrictEqual(expect.objectContaining({
	message: 'baz',
	}));

However, these test codes can be simplified by using .toMatchObject(...) without using expect.objectContaining(...) matchers.

-                    .toStrictEqual(expect.objectContaining({
+                    .toMatchObject({
                         code: 'ENOENT',
-                    }));
+                    });