vercel-cli 41.1.0__tar.gz

vercel_cli-41.1.0/.gitignore

@@ -0,0 +1,5 @@
+.DS_Store
+*.pyc
+.coverage
+.venv
+/dist/

vercel_cli-41.1.0/PKG-INFO

@@ -0,0 +1,188 @@
+Metadata-Version: 2.4
+Name: vercel-cli
+Version: 41.1.0
+Summary: Vercel CLI packaged for Python (bundled Node.js, vendored npm)
+Requires-Python: >=3.8
+Requires-Dist: nodejs-wheel-binaries==22.16.0
+Description-Content-Type: text/markdown
+
+# Python package wrapper for Vercel CLI
+
+[![CI](https://github.com/nuage-studio/vercel-cli-python/actions/workflows/test.yml/badge.svg)](https://github.com/nuage-studio/vercel-cli-python/actions/workflows/test.yml)
+[![codecov](https://codecov.io/gh/nuage-studio/vercel-cli-python/graph/badge.svg)](https://codecov.io/gh/nuage-studio/vercel-cli-python)
+[![Supported Python Versions](https://img.shields.io/badge/python-3.8--3.13-blue.svg)](https://www.python.org/)
+
+**vercel-cli** packages the npm `vercel` CLI for Python environments. It vendors the npm package under `vercel_cli/vendor/` and uses the bundled Node.js runtime provided by `nodejs-wheel-binaries`, so you can run `vercel` without installing Node.js.
+
+It provides both a command-line interface and a Python API that other libraries can use programmatically instead of resorting to subprocess calls.
+
+## Quick start
+
+- **Install**:
+
+```bash
+pip install vercel-cli
+```
+
+- **Use** (same arguments and behavior as the official npm CLI):
+
+```bash
+vercel --version
+vercel login
+vercel deploy
+```
+
+- **Use programmatically in Python** (for libraries that depend on this package):
+
+```python
+from vercel_cli import run_vercel
+
+# Deploy current directory
+exit_code = run_vercel(["deploy"])
+
+# Deploy specific directory with custom environment
+exit_code = run_vercel(
+    ["deploy", "--prod"],
+    cwd="/path/to/project",
+    env={"VERCEL_TOKEN": "my-token"}
+)
+
+# Check version
+exit_code = run_vercel(["--version"])
+```
+
+## What this provides
+
+- **No system Node.js required**: The CLI runs via the Node binary from `nodejs-wheel-binaries` (currently Node 22.x).
+- **Vendored npm package**: The `vercel` npm package (production deps only) is checked into `vercel_cli/vendor/`.
+- **Console entrypoint**: The `vercel` command maps to `vercel_cli.run:main`, which executes `vercel_cli/vendor/dist/vc.js` with the bundled Node runtime.
+- **Python API**: The `run_vercel()` function allows other Python libraries to use Vercel CLI programmatically without subprocess calls, with secure environment variable handling.
+
+## Requirements
+
+- Python 3.8+
+- macOS, Linux, or Windows supported by the Node wheels
+
+## How it works
+
+At runtime, `vercel_cli.run` locates `vercel_cli/vendor/dist/vc.js` and launches it via the Node executable exposed by `nodejs_wheel_binaries`. CLI arguments are passed through unchanged, while environment variables are handled securely.
+
+## Programmatic usage
+
+When using this package as a dependency in other Python libraries, you can call Vercel CLI commands directly without using subprocess:
+
+```python
+from vercel_cli import run_vercel
+import tempfile
+import os
+
+def deploy_my_app(source_dir: str, token: str) -> bool:
+    """Deploy an application to Vercel programmatically."""
+    with tempfile.TemporaryDirectory() as temp_dir:
+        # Copy your app to temp directory and modify as needed
+        # ...
+
+        # Deploy with custom environment
+        env = {
+            "VERCEL_TOKEN": token,
+            "NODE_ENV": "production"
+        }
+
+        exit_code = run_vercel(
+            ["deploy", "--prod", "--yes"],
+            cwd=temp_dir,
+            env=env
+        )
+
+        return exit_code == 0
+
+# Usage
+success = deploy_my_app("./my-app", "my-vercel-token")
+```
+
+The `run_vercel()` function accepts:
+
+- `args`: List of CLI arguments (same as command line)
+- `cwd`: Working directory for the command
+- `env`: Environment variables to set (passed directly to the Node.js runtime)
+
+## Security considerations
+
+When using the `env` parameter, only explicitly provided environment variables are passed to the Vercel CLI. This prevents accidental leakage of sensitive environment variables from your Python process while still allowing you to set necessary variables like `VERCEL_TOKEN`.
+
+Example with secure token handling:
+
+```python
+from vercel_cli import run_vercel
+
+# Secure: only VERCEL_TOKEN is passed to the CLI
+exit_code = run_vercel(
+    ["deploy", "--prod"],
+    env={"VERCEL_TOKEN": "your-secure-token"}
+)
+```
+
+This approach avoids common security pitfalls of subprocess environment variable handling.
+
+## Updating the vendored Vercel CLI (maintainers)
+
+There are two ways to update the vendored npm package under `vercel_cli/vendor/`:
+
+1) Manual update to a specific version
+
+```bash
+# Using the console script defined in pyproject.toml
+uv run update-vendor 46.0.2
+# or equivalently
+uv run python scripts/update_vendor.py 46.0.2
+```
+
+This will:
+
+- fetch `vercel@46.0.2` from npm,
+- verify integrity/shasum,
+- install production dependencies with `npm install --omit=dev`, and
+- copy the result into `vercel_cli/vendor/`.
+
+1) Automatic check-and-release (GitHub Actions)
+
+The workflow `.github/workflows/release.yml` checks npm `latest` and, if newer than the vendored version, will:
+
+- vendor the new version using `scripts/check_and_update.py`,
+- commit the changes and create a tag `v<version>`,
+- build distributions, and
+- publish to PyPI (requires `PYPI_API_TOKEN`).
+
+## Versioning
+
+The Python package version is derived dynamically from the vendored `package.json` via Hatch’s version source:
+
+```toml
+[tool.hatch.version]
+path = "vercel_cli/vendor/package.json"
+pattern = '"version"\s*:\s*"(?P<version>[^\\"]+)"'
+```
+
+## Development
+
+- Build backend: `hatchling`
+- Dependency management: `uv` (see `uv.lock`)
+- Tests: `pytest` with coverage in `tests/`
+- Lint/format: `ruff`; type-check: `basedpyright`
+
+Common commands (using `uv`):
+
+```bash
+# Run tests with coverage
+uv run pytest --cov=vercel_cli --cov-report=term-missing
+
+# Lint and format
+uv run ruff check .
+uv run ruff format .
+
+# Type-check
+uv run basedpyright
+
+# Build wheel and sdist
+uv run --with build python -m build
+```

vercel_cli-41.1.0/README.md

@@ -0,0 +1,180 @@
+# Python package wrapper for Vercel CLI
+
+[![CI](https://github.com/nuage-studio/vercel-cli-python/actions/workflows/test.yml/badge.svg)](https://github.com/nuage-studio/vercel-cli-python/actions/workflows/test.yml)
+[![codecov](https://codecov.io/gh/nuage-studio/vercel-cli-python/graph/badge.svg)](https://codecov.io/gh/nuage-studio/vercel-cli-python)
+[![Supported Python Versions](https://img.shields.io/badge/python-3.8--3.13-blue.svg)](https://www.python.org/)
+
+**vercel-cli** packages the npm `vercel` CLI for Python environments. It vendors the npm package under `vercel_cli/vendor/` and uses the bundled Node.js runtime provided by `nodejs-wheel-binaries`, so you can run `vercel` without installing Node.js.
+
+It provides both a command-line interface and a Python API that other libraries can use programmatically instead of resorting to subprocess calls.
+
+## Quick start
+
+- **Install**:
+
+```bash
+pip install vercel-cli
+```
+
+- **Use** (same arguments and behavior as the official npm CLI):
+
+```bash
+vercel --version
+vercel login
+vercel deploy
+```
+
+- **Use programmatically in Python** (for libraries that depend on this package):
+
+```python
+from vercel_cli import run_vercel
+
+# Deploy current directory
+exit_code = run_vercel(["deploy"])
+
+# Deploy specific directory with custom environment
+exit_code = run_vercel(
+    ["deploy", "--prod"],
+    cwd="/path/to/project",
+    env={"VERCEL_TOKEN": "my-token"}
+)
+
+# Check version
+exit_code = run_vercel(["--version"])
+```
+
+## What this provides
+
+- **No system Node.js required**: The CLI runs via the Node binary from `nodejs-wheel-binaries` (currently Node 22.x).
+- **Vendored npm package**: The `vercel` npm package (production deps only) is checked into `vercel_cli/vendor/`.
+- **Console entrypoint**: The `vercel` command maps to `vercel_cli.run:main`, which executes `vercel_cli/vendor/dist/vc.js` with the bundled Node runtime.
+- **Python API**: The `run_vercel()` function allows other Python libraries to use Vercel CLI programmatically without subprocess calls, with secure environment variable handling.
+
+## Requirements
+
+- Python 3.8+
+- macOS, Linux, or Windows supported by the Node wheels
+
+## How it works
+
+At runtime, `vercel_cli.run` locates `vercel_cli/vendor/dist/vc.js` and launches it via the Node executable exposed by `nodejs_wheel_binaries`. CLI arguments are passed through unchanged, while environment variables are handled securely.
+
+## Programmatic usage
+
+When using this package as a dependency in other Python libraries, you can call Vercel CLI commands directly without using subprocess:
+
+```python
+from vercel_cli import run_vercel
+import tempfile
+import os
+
+def deploy_my_app(source_dir: str, token: str) -> bool:
+    """Deploy an application to Vercel programmatically."""
+    with tempfile.TemporaryDirectory() as temp_dir:
+        # Copy your app to temp directory and modify as needed
+        # ...
+
+        # Deploy with custom environment
+        env = {
+            "VERCEL_TOKEN": token,
+            "NODE_ENV": "production"
+        }
+
+        exit_code = run_vercel(
+            ["deploy", "--prod", "--yes"],
+            cwd=temp_dir,
+            env=env
+        )
+
+        return exit_code == 0
+
+# Usage
+success = deploy_my_app("./my-app", "my-vercel-token")
+```
+
+The `run_vercel()` function accepts:
+
+- `args`: List of CLI arguments (same as command line)
+- `cwd`: Working directory for the command
+- `env`: Environment variables to set (passed directly to the Node.js runtime)
+
+## Security considerations
+
+When using the `env` parameter, only explicitly provided environment variables are passed to the Vercel CLI. This prevents accidental leakage of sensitive environment variables from your Python process while still allowing you to set necessary variables like `VERCEL_TOKEN`.
+
+Example with secure token handling:
+
+```python
+from vercel_cli import run_vercel
+
+# Secure: only VERCEL_TOKEN is passed to the CLI
+exit_code = run_vercel(
+    ["deploy", "--prod"],
+    env={"VERCEL_TOKEN": "your-secure-token"}
+)
+```
+
+This approach avoids common security pitfalls of subprocess environment variable handling.
+
+## Updating the vendored Vercel CLI (maintainers)
+
+There are two ways to update the vendored npm package under `vercel_cli/vendor/`:
+
+1) Manual update to a specific version
+
+```bash
+# Using the console script defined in pyproject.toml
+uv run update-vendor 46.0.2
+# or equivalently
+uv run python scripts/update_vendor.py 46.0.2
+```
+
+This will:
+
+- fetch `vercel@46.0.2` from npm,
+- verify integrity/shasum,
+- install production dependencies with `npm install --omit=dev`, and
+- copy the result into `vercel_cli/vendor/`.
+
+1) Automatic check-and-release (GitHub Actions)
+
+The workflow `.github/workflows/release.yml` checks npm `latest` and, if newer than the vendored version, will:
+
+- vendor the new version using `scripts/check_and_update.py`,
+- commit the changes and create a tag `v<version>`,
+- build distributions, and
+- publish to PyPI (requires `PYPI_API_TOKEN`).
+
+## Versioning
+
+The Python package version is derived dynamically from the vendored `package.json` via Hatch’s version source:
+
+```toml
+[tool.hatch.version]
+path = "vercel_cli/vendor/package.json"
+pattern = '"version"\s*:\s*"(?P<version>[^\\"]+)"'
+```
+
+## Development
+
+- Build backend: `hatchling`
+- Dependency management: `uv` (see `uv.lock`)
+- Tests: `pytest` with coverage in `tests/`
+- Lint/format: `ruff`; type-check: `basedpyright`
+
+Common commands (using `uv`):
+
+```bash
+# Run tests with coverage
+uv run pytest --cov=vercel_cli --cov-report=term-missing
+
+# Lint and format
+uv run ruff check .
+uv run ruff format .
+
+# Type-check
+uv run basedpyright
+
+# Build wheel and sdist
+uv run --with build python -m build
+```

vercel_cli-41.1.0/pyproject.toml

@@ -0,0 +1,78 @@
+[project]
+name = "vercel-cli"
+dynamic = ["version"]
+description = "Vercel CLI packaged for Python (bundled Node.js, vendored npm)"
+readme = "README.md"
+requires-python = ">=3.8"
+dependencies = [
+    "nodejs-wheel-binaries==22.16.0",
+]
+
+[dependency-groups]
+dev = [
+    "basedpyright>=1.31.3",
+    "pytest-cov>=5.0.0",
+    "ruff>=0.12.10",
+]
+
+[project.scripts]
+vercel = "vercel_cli.run:main"
+vendor = "vercel_cli.vendor_cli:main"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build]
+include = ["vercel_cli/vendor/**"]
+
+[tool.hatch.build.targets.wheel]
+packages = ["vercel_cli"]
+
+[tool.hatch.version]
+# Extract the version from the vendored package.json
+path = "vercel_cli/vendor/package.json"
+pattern = '"version"\s*:\s*"(?P<version>[^\"]+)"'
+
+
+[tool.pytest.ini_options]
+addopts = "--cov --cov-branch --cov-report=term-missing"
+testpaths = ["tests"]
+
+[tool.ruff]
+# https://docs.astral.sh/ruff/settings/
+preview = true
+line-length = 88
+target-version = "py38"
+
+[tool.ruff.lint]
+select = ["ALL"]
+ignore = [
+    "CPY001", # We don't want warnings about missing Copyrights because it's private code
+    "TID252", # Nuage team disagrees about relative imports: we find them more readable
+    # Opinionated choices for conflicting rules
+    "D203",   # 1 blank line required before class docstring (we prefer D211: no blank line)
+    "D213",   # Multi-line docstring summary should start at the second line (we prefer D212: first line)
+    "COM812", # Trailing comma missing (conflicts with formatter, let formatter handle it)
+]
+exclude = [".venv"]
+
+[tool.ruff.format]
+preview = true
+skip-magic-trailing-comma = true
+
+[tool.ruff.lint.per-file-ignores]
+"tests/*.py" = [
+    "S",    # none of these security focused rules are relevant for tests/build scripts
+    "D100", # Allow missing module docstrings in tests
+    "D103", # Allow missing function docstrings in tests
+    "S101", # Allow assert in tests
+    "PLR2004", # Allow magic numbers in tests
+]
+
+[tool.ruff.lint.isort]
+split-on-trailing-comma = false  # Align with formatter's skip-magic-trailing-comma = true
+
+[tool.pyright]
+pythonVersion = "3.8"
+typeCheckingMode = "strict"

vercel_cli-41.1.0/vercel_cli/vendor/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2017 Vercel, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.