Sign In

@cross-deck/cli

Package Overview
Dependencies
Maintainers
1
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cross-deck/cli - npm Package Compare versions

Comparing version
1.4.0
to
1.4.1
+1
-1
package.json
{
"name": "@cross-deck/cli",
"version": "1.4.0",
"version": "1.4.1",
"description": "Crossdeck CLI — upload source maps so production stack traces resolve back to original file:line:function.",

@@ -5,0 +5,0 @@ "license": "MIT",

@@ -8,10 +8,26 @@ # @cross-deck/cli

npm i -g @cross-deck/cli
crossdeck login # sign in through your browser
crossdeck init --name "My App" --platform web
crossdeck # opens the session — a working environment
```
That's a real project, a real publishable key, and a copy-paste SDK snippet in
under a minute — the same result as clicking through onboarding in the dashboard,
headless.
`crossdeck` on an interactive terminal opens a **session** (like `claude`). Inside
it you type bare commands with no prefix, and your active project persists across
the whole session and shows in the prompt:
```
prolend ❯ login # sign in through your browser
prolend ❯ init --name "My App" --platform web
prolend ❯ revenue
prolend ❯ exit
```
**Two ways to drive it — same engine.** Prefer one-shot commands? Everything is
*also* a plain command, no session: `crossdeck login`, `crossdeck init …`,
`crossdeck revenue`. Use the session by hand; use one-shot in scripts and CI.
Crossdeck opens a session **only** on an interactive terminal — a pipe or CI
runner runs the command and exits, never trapped in a REPL.
> **New to Crossdeck?** The docs have a word-for-word walkthrough from a blank
> machine to a live project with identity wired and a payment rail connected:
> **[cross-deck.com/docs/cli → Zero to a running account](https://cross-deck.com/docs/cli#arc)**.
---

@@ -55,3 +71,6 @@

file; the 1-hour access token lives in memory only and is never written to disk,
argv, or logs. Revoke anytime from **Settings → Developer** or `crossdeck logout`.
argv, or logs. **`crossdeck logout` revokes this machine's session server-side**
(RFC 7009) and then wipes the local file — a stolen `credentials.json` is dead the
moment you log out. Manage and revoke every connected machine from the dashboard's
**Settings → Developer → Connected apps**.

@@ -77,4 +96,6 @@ ### Zero to installed

Install — web
import { crossdeck } from "@cross-deck/web";
crossdeck.init({ publishableKey: "cd_pub_live_…" });
import { Crossdeck } from "@cross-deck/web";
Crossdeck.init({ publishableKey: "cd_pub_live_…" });
// after your user signs in:
await Crossdeck.identify(currentUser.id);
```

@@ -81,0 +102,0 @@

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

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

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

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