dodopayments-cli 2.0.0

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,125 @@
+name: Bug Report
+description: Report a bug or unexpected behavior
+title: "[Bug]: "
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! Please fill out the form below to help us understand and fix the issue.
+
+  - type: checkboxes
+    id: existing-issue
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+
+  - type: dropdown
+    id: command
+    attributes:
+      label: CLI Command
+      description: Which command is affected?
+      options:
+        - dodo login
+        - dodo products
+        - dodo payments
+        - dodo customers
+        - dodo discounts
+        - dodo licences
+        - dodo wh (webhooks)
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of what the bug is.
+      placeholder: Describe the bug...
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior
+      placeholder: |
+        1. Run 'dodo ...'
+        2. Select '...'
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Error Logs
+      description: Please copy and paste any relevant error messages or logs. This will be automatically formatted into code.
+      render: shell
+
+  - type: input
+    id: version
+    attributes:
+      label: CLI Version
+      description: What version of the CLI are you running? (Check package.json or npm list -g dodopayments-cli)
+      placeholder: e.g., 0.1.0
+    validations:
+      required: true
+
+  - type: input
+    id: runtime
+    attributes:
+      label: Runtime & Version
+      description: Are you using Bun or Node? What version? (Run `bun --version` or `node --version`)
+      placeholder: e.g., Bun 1.1.0 or Node 20.10.0
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating System
+      options:
+        - macOS
+        - Windows
+        - Linux
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: mode
+    attributes:
+      label: Environment Mode
+      description: Were you using test mode or live mode?
+      options:
+        - Test Mode
+        - Live Mode
+        - Not applicable
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord Community
+    url: https://discord.gg/bYqAp4ayYh
+    about: Join our Discord for questions, help, and community discussions
+  - name: Dodo Payments Documentation
+    url: https://docs.dodopayments.com
+    about: Check out our documentation for guides and API reference
+  - name: Security Vulnerability
+    url: https://github.com/dodopayments/dodopayments-cli/security/advisories/new
+    about: Report a security vulnerability privately

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,88 @@
+name: Feature Request
+description: Suggest a new feature or enhancement
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a feature! Please fill out the form below to help us understand your request.
+
+  - type: checkboxes
+    id: existing-issue
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if a feature request already exists.
+      options:
+        - label: I have searched the existing issues
+          required: true
+
+  - type: dropdown
+    id: feature-type
+    attributes:
+      label: Feature Type
+      description: What type of feature is this?
+      options:
+        - New CLI command
+        - Enhancement to existing command
+        - New webhook event support
+        - Output/formatting improvement
+        - Documentation
+        - Performance improvement
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: Is your feature request related to a problem? Please describe.
+      placeholder: A clear description of what the problem is. Ex. I'm always frustrated when...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the solution you'd like
+      placeholder: A clear description of what you want to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Describe any alternative solutions or features you've considered.
+
+  - type: dropdown
+    id: command
+    attributes:
+      label: Related Command (if applicable)
+      description: Is this feature related to a specific command?
+      options:
+        - Not command-specific
+        - dodo login
+        - dodo products
+        - dodo payments
+        - dodo customers
+        - dodo discounts
+        - dodo licences
+        - dodo wh (webhooks)
+        - New command
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context, screenshots, or examples about the feature request here.
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      description: Would you be willing to contribute this feature?
+      options:
+        - label: I would be willing to submit a PR for this feature

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,69 @@
+## Description
+
+<!-- Provide a brief description of the changes in this PR -->
+
+## Related Issue
+
+<!-- Link to the issue this PR addresses (if applicable) -->
+<!-- Use "Fixes #123" or "Closes #123" to automatically close the issue when merged -->
+
+Fixes #
+
+## Type of Change
+
+<!-- Mark the appropriate option with an "x" -->
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] New CLI command
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Refactoring (no functional changes)
+
+## Changes Made
+
+<!-- Describe the changes in detail -->
+
+-
+-
+-
+
+## Testing
+
+<!-- Describe how you tested your changes -->
+
+### Test Environment
+
+- Runtime (Bun/Node) version:
+- OS:
+
+### Test Cases
+
+<!-- List the test cases you've verified -->
+
+- [ ] Tested in test mode
+- [ ] Tested in live mode (if applicable)
+- [ ] Tested on macOS
+- [ ] Tested on Windows
+- [ ] Tested on Linux
+- [ ] Other: <!-- specify -->
+
+## Checklist
+
+<!-- Mark completed items with an "x" -->
+
+- [ ] My code follows the project's coding guidelines
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation (README.md)
+- [ ] My changes generate no new warnings
+- [ ] I have tested my changes locally with `bun run index.ts`
+- [ ] The build passes with `bun run build`
+
+## Screenshots (if applicable)
+
+<!-- Add screenshots or terminal output to help explain your changes -->
+
+## Additional Notes
+
+<!-- Add any additional context or notes for reviewers -->

package/.github/workflows/publish.yml

@@ -0,0 +1,63 @@
+name: Publish to npm on tag
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          registry-url: 'https://registry.npmjs.org'
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 'latest'
+
+      - name: Update package.json version from release tag
+        env:
+          TAG_NAME: ${{ github.ref_name }}
+        run: |
+          echo "TAG_NAME=${TAG_NAME}"
+          TAG_STRIPPED="${TAG_NAME#v}"
+          echo "Updating package.json version to: ${TAG_STRIPPED}"
+          
+          # Update package.json version using node
+          node -e "
+            const fs = require('fs');
+            const pkg = JSON.parse(fs.readFileSync('./package.json', 'utf8'));
+            pkg.version = '${TAG_STRIPPED}';
+            fs.writeFileSync('./package.json', JSON.stringify(pkg, null, 2) + '\n');
+            console.log('Updated package.json version to:', pkg.version);
+          "
+          
+          # Verify the update
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          echo "package.json version after update: ${PKG_VERSION}"
+          if [ "${TAG_STRIPPED}" != "${PKG_VERSION}" ]; then
+            echo "::error::Failed to update package.json version"
+            exit 1
+          fi
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Build
+        run: bun run build
+
+      - name: Publish to npm
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm publish --provenance --access public

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**[support@dodopayments.com](mailto:support@dodopayments.com)**.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,200 @@
+# Contributing to Dodo Payments CLI
+
+First off, thank you for considering contributing to the Dodo Payments CLI! It's people like you that make this tool great for everyone.
+
+We welcome contributions of all kinds - bug reports, feature requests, documentation improvements, and code contributions.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [Project Structure](#project-structure)
+- [How to Contribute](#how-to-contribute)
+- [Coding Guidelines](#coding-guidelines)
+- [Pull Request Process](#pull-request-process)
+- [Adding New Commands](#adding-new-commands)
+- [Community](#community)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our [Code of Conduct](./CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [support@dodopayments.com](mailto:support@dodopayments.com).
+
+## Getting Started
+
+### Prerequisites
+
+- [Bun](https://bun.sh/) >= 1.0 (recommended) or Node.js >= 18
+- A Dodo Payments account (for testing)
+
+### Development Setup
+
+1. **Fork the repository** on GitHub
+
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/dodopayments-cli.git
+   cd dodopayments-cli
+   ```
+
+3. **Install dependencies**:
+   ```bash
+   bun install
+   ```
+
+4. **Create a branch** for your changes:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+5. **Run the CLI locally**:
+   ```bash
+   bun run index.ts <command>
+   ```
+
+6. **Build the project**:
+   ```bash
+   bun run build
+   ```
+
+## Project Structure
+
+```
+dodopayments-cli/
+├── index.ts              # Main CLI entrypoint
+├── utils/                # Utility functions
+├── dodo-webhooks/        # Webhook testing functionality
+├── .github/
+│   ├── ISSUE_TEMPLATE/   # Issue templates
+│   ├── PULL_REQUEST_TEMPLATE.md
+│   └── workflows/        # CI/CD workflows
+├── CONTRIBUTING.md       # This file
+├── CODE_OF_CONDUCT.md
+├── LICENSE
+└── README.md
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before creating a bug report, please check existing issues to avoid duplicates. When creating a bug report, include:
+
+- A clear, descriptive title
+- Steps to reproduce the issue
+- Expected behavior vs actual behavior
+- Your environment (OS, Bun/Node version, CLI version)
+- Any relevant error messages or logs
+
+### Suggesting Features
+
+Feature requests are welcome! Please include:
+
+- A clear description of the feature
+- The problem it solves or use case it addresses
+- Any alternative solutions you've considered
+
+### Contributing Code
+
+1. Check the [issues](https://github.com/dodopayments/dodopayments-cli/issues) for open tasks
+2. Comment on an issue to let others know you're working on it
+3. Follow the [coding guidelines](#coding-guidelines)
+4. Submit a [pull request](#pull-request-process)
+
+## Coding Guidelines
+
+### General Principles
+
+- **Use TypeScript**: All code should be written in TypeScript
+- **Use Bun APIs**: Prefer Bun's built-in APIs when available
+- **Keep it simple**: Write clear, readable code
+- **Add comments**: Document complex logic and non-obvious decisions
+
+### Code Style
+
+- Use 2 spaces for indentation
+- Use single quotes for strings
+- Add semicolons at end of statements
+- Use `const` by default, `let` when reassignment is needed
+
+### CLI Design Principles
+
+- **Interactive by default**: Use prompts for required inputs when not provided as arguments
+- **Helpful error messages**: Provide clear, actionable error messages
+- **Consistent output**: Use consistent formatting across all commands
+
+## Pull Request Process
+
+1. **Update documentation** if you're adding or changing functionality
+
+2. **Follow the PR template** - Fill out all sections completely
+
+3. **Link related issues** - Reference any issues your PR addresses
+
+4. **Keep PRs focused** - One feature or fix per PR
+
+5. **Write clear commit messages** - Describe what and why
+
+6. **Ensure the build passes** - Run `bun run build` before submitting
+
+7. **Request review** - Tag maintainers for review
+
+## Adding New Commands
+
+To add a new command to the CLI:
+
+1. **Add the command handler** in `index.ts`:
+   ```typescript
+   case 'your-command':
+     await handleYourCommand();
+     break;
+   ```
+
+2. **Implement the handler function**:
+   - Use `inquirer` for interactive prompts
+   - Use the `dodopayments` SDK for API calls
+   - Handle errors gracefully with helpful messages
+
+3. **Update the README** with documentation for the new command
+
+4. **Test thoroughly** in both test and live modes
+
+### Example Command Structure
+
+```typescript
+async function handleYourCommand() {
+  // 1. Parse any arguments
+  const args = process.argv.slice(3);
+  
+  // 2. Prompt for missing inputs
+  const answers = await inquirer.prompt([
+    {
+      type: 'input',
+      name: 'someInput',
+      message: 'Enter value:',
+    }
+  ]);
+  
+  // 3. Make API call
+  const result = await dodo.someResource.someMethod({
+    // ...
+  });
+  
+  // 4. Display results
+  console.log(result);
+}
+```
+
+## Community
+
+- **Discord**: [Join our community](https://discord.gg/bYqAp4ayYh) for help and discussion
+- **GitHub Issues**: For bug reports and feature requests
+- **Twitter**: Follow [@dodopayments](https://twitter.com/dodopayments) for updates
+
+## Recognition
+
+We appreciate all contributors! Your contributions help make the Dodo Payments CLI better for everyone.
+
+---
+
+Thank you for contributing to Dodo Payments CLI!