🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@primitivedotdev/cli

Package Overview
Dependencies
Maintainers
2
Versions
61
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@primitivedotdev/cli - npm Package Compare versions

Comparing version
1.13.2
to
1.13.3
+1
-1
package.json
{
"name": "@primitivedotdev/cli",
"version": "1.13.2",
"version": "1.13.3",
"description": "Official Primitive CLI: deploy Primitive Functions, send and inspect mail, manage endpoints, all from the terminal. Wraps the @primitivedotdev/sdk runtime client with one-shot commands.",

@@ -5,0 +5,0 @@ "type": "module",

@@ -102,8 +102,8 @@ # @primitivedotdev/cli

# Payer (recommended): pay the email challenge in one step. Signs the challenge
# locally with your wallet key AND sends the signed interaction.json in-thread,
# so you skip the manual sign-then-send dance. --in-reply-to is the inbound
# challenge email you received; it is fetched to address the payment to the
# payee and thread it under the challenge, with From defaulting to the payer it
# was sent to. The message carries a short default note alongside the
# attachment; pass --body to customize it.
# locally with your wallet key AND sends the signed interaction.json, so you
# skip the manual sign-then-send dance. --in-reply-to is the inbound challenge
# email you received; it is fetched to address the payment to the payee, with
# From defaulting to the payer it was sent to. The send is not threaded under
# the challenge (the payment associates by interaction_id). The message carries
# a short default note alongside the attachment; pass --body to customize it.
primitive payments pay-email --challenge-file challenge.json \

@@ -110,0 +110,0 @@ --in-reply-to <inbound-challenge-email-id> --wait

Sorry, the diff of this file is too big to display