@xmtp/content-type-remote-attachment - npm Package Compare versions

Comparing version 1.1.4 to 1.1.5

package.json

		{
		"name": "@xmtp/content-type-remote-attachment",
		"version": "1.1.4",
		"version": "1.1.5",
		"description": "An XMTP content type to support sending file attachments that are stored off network",
		@@ -20,2 +20,5 @@ "author": "XMTP Labs <eng@xmtp.com>",
		},
		"files": [
		"dist"
		],
		"sideEffects": false,
		@@ -22,0 +25,0 @@ "repository": {

README.md

		# Remote attachment content type

		![Status](https://img.shields.io/badge/Content_type_status-Standards--track-yellow) ![Status](https://img.shields.io/badge/Reference_implementation_status-Stable-brightgreen)

		The [remote-attachment](https://github.com/xmtp/xmtp-js-content-types/tree/main/remote-attachment) package provides an XMTP content type to support sending file attachments that are stored off-network. Use it to enable your app to send and receive message attachments.
		@@ -133,7 +135,7 @@
		contentType: ContentTypeRemoteAttachment,
		contentFallback: "a screenshot of 1MB of text",
		});
		```

		Note that we’re using `contentFallback` to enable clients that don't support these content types to still display something. For cases where clients do support these types, they can use the content fallback as alt text for accessibility purposes.
		> Note
		> `contentFallback` text is provided by the codec and gives clients that _don't_ support a content type the option to display some useful context. For cases where clients do support the content type, they can use the content fallback as alt text for accessibility purposes.

		@@ -140,0 +142,0 @@ ## Receive a remote attachment

.eslintrc.cjs

.turbo/turbo-build.log

CHANGELOG.md

src/Attachment.test.ts

src/Attachment.ts

src/encryption.ts

src/index.ts

src/RemoteAttachment.test.ts

src/RemoteAttachment.ts

src/utils.ts

tsconfig.eslint.json

tsconfig.json

tsup.config.ts

vitest.config.ts

vitest.setup.ts

New alerts