@tapjs/snapshot - npm Package Compare versions

Comparing version 0.0.0-17 to 0.0.0-18

package.json

		{
		"name": "@tapjs/snapshot",
		"version": "0.0.0-17",
		"version": "0.0.0-18",
		"description": "",
		@@ -40,3 +40,3 @@ "author": "Isaac Z. Schlueter <i@izs.me> (https://blog.izs.me)",
		"peerDependencies": {
		"@tapjs/core": "0.0.0-17"
		"@tapjs/core": "0.0.0-18"
		},
		@@ -43,0 +43,0 @@ "dependencies": {

README.md

		@@ -47,3 +47,4 @@ # `@tapjs/snapshot`
		that we either make the tests less comprehensive, or even worse,
		treat some as "known failures".
		treat some as ["known
		failures"](https://node-tap.org/basics/#note-about-%22expected-failures%22-and-%22run-until-good%22-testing).

		@@ -124,6 +125,6 @@ ## Testing Output with Snapshots
		then it will be converted to a string using
		[tcompare.format](http://npm.im/tcompare). This is typically
		pretty easy for humans to understand, but of course if you prefer
		to use `JSON.stringify` or something else, you can do so easily
		enough. The
		[tcompare.format](https://tapjs.github.io/tapjs/modules/tcompare.html).
		This is typically pretty easy for humans to understand, but of
		course if you prefer to use `JSON.stringify` or something else,
		you can do so easily enough. The
		[t.formatSnapshot](https://tapjs.github.io/tapjs/classes/_tapjs_test.index.Test.html#formatSnapshot)
		@@ -291,3 +292,6 @@ can be used to customize this for an entire test.
		// it'll always store it as the actual path.
		t.snapshotFile = new URL('../tap-snapshots/foo.test.cjs', import.meta.url)
		t.snapshotFile = new URL(
		'../tap-snapshots/foo.test.cjs',
		import.meta.url
		)
		t.matchSnapshot('foo')
		@@ -298,3 +302,6 @@ })
		// this writes to ./test/tap-snapshots/bar.test.cjs'
		t.snapshotFile = new URL('../tap-snapshots/bar.test.cjs', import.meta.url)
		t.snapshotFile = new URL(
		'../tap-snapshots/bar.test.cjs',
		import.meta.url
		)
		t.matchSnapshot('bar')
		@@ -301,0 +308,0 @@ })

New alerts