@somewhatabstract/x 0.1.0 → 0.1.1

package/README.md

@@ -1,12 +1,13 @@
 # x
 
-Execute any bin defined by any package in a monorepo without needing to install that package.
+Execute any bin defined by any package within a monorepo without needing to install that package at the root.
 
 ## Overview
 
 `x` is a tool for monorepos that allows you to execute binary scripts from any package in your workspace without installing them globally or in your current package. It automatically discovers all packages in your workspace and finds the matching bin script.
 
 **Supports multiple package managers:**
+
 - 📦 npm workspaces
 - 🧶 Yarn (classic and modern)
 - 📌 pnpm workspaces
@@ -28,32 +29,16 @@ yarn global add @somewhatabstract/x
 
 ```bash
 # Execute a bin script from any package in the workspace
-x <script-name> [...args]
+x <script-name> [-- <args...>]
 
 # Preview what would be executed (dry-run mode)
 x --dry-run <script-name>
 
-# Pass arguments to the script
-x tsc --noEmit
-x eslint src/ --fix
-x jest --watch
+# Pass arguments to the script (use `--` when args might look like x's own options)
+x my-script -- --flag value
 ```
 
-### Examples
-
-```bash
-# Run TypeScript compiler from any package that provides it
-x tsc --noEmit
-
-# Run ESLint from any package in the workspace
-x eslint src/
-
-# Preview which jest binary would be executed
-x --dry-run jest
-
-# Run a custom script with arguments
-x my-custom-script arg1 arg2
-```
+This only executes bin scripts defined by packages in your workspace, not their dependencies. The bin must be an executable file with a shebang (on Unix-like systems) or a directly runnable file (on Windows), or a JS script that can be executed with Node.js.
 
 ## Features
 
@@ -71,7 +56,9 @@ x my-custom-script arg1 arg2
 1. **Workspace Detection**: Uses `@manypkg/find-root` to find the workspace root (supports npm, Yarn, pnpm, Lerna, Bun, Rush)
 2. **Package Discovery**: Uses `@manypkg/get-packages` to discover all packages in the workspace
 3. **Bin Matching**: Searches through package.json files to find bins matching your requested script name
-4. **Execution**: Executes the matched script directly via the OS (on Unix-like systems this requires an executable file with a shebang; on Windows the bin must be a directly runnable file such as a `.exe`, `.cmd`, or `.bat`)
+4. **Execution**: Executes the matched script either directly via the OS or via Node.js:
+   - **Direct OS execution**: On Unix-like systems this requires an executable file with a shebang; on Windows the bin must be a directly runnable file such as a `.exe`, `.cmd`, or `.bat`.
+   - **Node.js execution**: If the bin is a JS file, it is executed with Node.js.
 
 ## Requirements
 
@@ -113,21 +100,6 @@ pnpm build
 ./dist/x.mjs <script-name>
 ```
 
-## Architecture
-
-The implementation follows a modular design with separate concerns:
-
-- `errors.ts` - Custom error types for user-friendly messages
-- `find-workspace-root.ts` - Workspace root detection using @manypkg/find-root
-- `discover-packages.ts` - Package discovery via @manypkg/get-packages
-- `find-matching-bins.ts` - Bin script matching logic
-- `execute-script.ts` - Direct script execution
-- `build-environment.ts` - npm/pnpm environment variable construction
-- `resolve-bin-path.ts` - Bin path resolution with security validation (path traversal protection)
-- `x-impl.ts` - Main orchestration logic
-- `bin/x.ts` - CLI entry point with yargs
-
 ## License
 
 MIT
-

package/package.json

@@ -8,8 +8,11 @@
   "bin": {
     "x": "./dist/x.mjs"
   },
+  "files": [
+    "dist"
+  ],
   "type": "module",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Execute any bin defined by any package in a monorepo without needing to install that package",
   "bugs": {
     "url": "https://github.com/somewhatabstract/x/issues"

package/.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

package/.changeset/config.json

@@ -1,11 +0,0 @@
-{
-    "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
-    "changelog": "@changesets/cli/changelog",
-    "commit": false,
-    "fixed": [],
-    "linked": [],
-    "access": "restricted",
-    "baseBranch": "main",
-    "updateInternalDependencies": "patch",
-    "ignore": []
-}

package/.github/codeql/codeql-config.yml

@@ -1,5 +0,0 @@
-name: X CodeQL config
-paths:
-  - "src"
-paths-ignore:
-  - src/__tests__

package/.github/dependabot.yml

@@ -1,28 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
-version: 2
-updates:
-  - package-ecosystem: npm
-    directory: "/"
-    schedule:
-      interval: weekly
-      day: saturday
-      time: "09:00"
-      timezone: America/Chicago
-    open-pull-requests-limit: 10
-    reviewers:
-      - somewhatabstract
-  
-  - package-ecosystem: github-actions
-    directory: "/"
-    schedule:
-      interval: weekly
-      day: saturday
-      time: "09:00"
-      timezone: America/Chicago
-    open-pull-requests-limit: 10
-    reviewers:
-      - somewhatabstract

package/.github/workflows/codeql-analysis.yml

@@ -1,71 +0,0 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-# ******** NOTE ********
-# We have attempted to detect the languages in your repository. Please check
-# the `language` matrix defined below to confirm you have the correct set of
-# supported CodeQL languages.
-#
-name: "CodeQL"
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    # The branches below must be a subset of the branches above
-    branches: [main]
-  schedule:
-    - cron: "16 7 * * 2"
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-    permissions:
-      actions: read
-      contents: read
-      security-events: write
-
-    strategy:
-      fail-fast: false
-      matrix:
-        language: ["javascript"]
-        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
-        # Learn more:
-        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-
-      # Initializes the CodeQL tools for scanning.
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@710e2945787622b429f8982cacb154faa182de18
-        with:
-          languages: ${{ matrix.language }}
-          # If you wish to specify custom queries, you can do so here or in a config file.
-          # By default, queries listed here will override any specified in a config file.
-          # Prefix the list here with "+" to use these queries and those in the config file.
-          # queries: ./path/to/local/query, your-org/your-repo/queries@main
-
-      # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
-      # If this step fails, then you should remove it and run the build manually (see below)
-      - name: Autobuild
-        uses: github/codeql-action/autobuild@710e2945787622b429f8982cacb154faa182de18
-
-      # ℹ️ Command-line programs to run using the OS shell.
-      # 📚 https://git.io/JvXDl
-
-      # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
-      #    and modify them (or add more) to build your code if your project
-      #    uses a compiled language
-
-      #- run: |
-      #   make bootstrap
-      #   make release
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@710e2945787622b429f8982cacb154faa182de18

package/.github/workflows/dependabot-pr-approval.yml

@@ -1,36 +0,0 @@
-name: Dependabot Pull Request Approve and Merge
-
-on: pull_request_target
-
-permissions:
-    pull-requests: write
-    contents: write
-
-jobs:
-    dependabot:
-        runs-on: ubuntu-latest
-        # Checking the actor will prevent your Action run failing on non-Dependabot
-        # PRs but also ensures that it only does work for Dependabot PRs.
-        if: ${{ github.actor == 'dependabot[bot]' }}
-        steps:
-            # This first step will fail if there's no metadata and so the approval
-            # will not occur.
-            - name: Dependabot metadata
-              id: dependabot-metadata
-              uses: dependabot/fetch-metadata@21025c705c08248db411dc16f3619e6b5f9ea21a
-              with:
-                  github-token: "${{ secrets.GITHUB_TOKEN }}"
-            # Here the PR gets approved.
-            - name: Approve a PR
-              run: gh pr review --approve "$PR_URL"
-              env:
-                  PR_URL: ${{ github.event.pull_request.html_url }}
-                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-            # Finally, this sets the PR to allow auto-merging for patch and minor
-            # updates if all checks pass
-            - name: Enable auto-merge for Dependabot PRs
-              if: ${{ steps.dependabot-metadata.outputs.update-type != 'version-update:semver-major' }}
-              run: gh pr merge --auto --squash "$PR_URL"
-              env:
-                  PR_URL: ${{ github.event.pull_request.html_url }}
-                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/.github/workflows/nodejs.yml

@@ -1,129 +0,0 @@
-name: Node CI
-
-on:
-  pull_request:
-    # ready_for_review is useful for when a PR is converted from "draft" to "not
-    # draft".
-    types: [edited, opened, synchronize, ready_for_review, reopened]
-
-  push:
-    branches:
-      - main
-
-jobs:
-  lint:
-    name: Lint and static types check
-    env:
-      CI: true
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ubuntu-latest]
-        node-version: [20.x]
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-
-      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061
-        name: Install pnpm
-        with:
-          run_install: false
-          package_json_file: "package.json"
-
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238
-        with:
-          node-version: ${{ matrix.node-version }}
-          cache: "pnpm"
-          cache-dependency-path: "pnpm-lock.yaml"
-
-      - name: Install Dependencies
-        shell: bash
-        run: pnpm install --frozen-lockfile
-
-      - name: Lint
-        run: pnpm lint
-
-      - name: Static Types
-        run: pnpm typecheck
-
-      - name: Changesets check
-        uses: Khan/actions@973e081efd07f23c4e521e7f4c6b15c9257ee924
-        if: |
-          github.actor != 'dependabot[bot]' &&
-          github.actor != 'dependabot-preview[bot]' &&
-          github.event_name == 'pull_request'
-        with:
-          exclude: .github/,.storybook/
-
-  coverage:
-    name: Update test coverage
-    env:
-      CI: true
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ubuntu-latest]
-        node-version: [20.x]
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-
-      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061
-        name: Install pnpm
-        with:
-          run_install: false
-          package_json_file: "package.json"
-
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238
-        with:
-          node-version: ${{ matrix.node-version }}
-          cache: "pnpm"
-          cache-dependency-path: "pnpm-lock.yaml"
-
-      - name: Install Dependencies
-        shell: bash
-        run: pnpm install --frozen-lockfile
-
-      - name: Run tests with coverage
-        run: pnpm coverage
-      - name: Upload coverage
-        uses: codecov/codecov-action@671740ac38dd9b0130fbe1cec585b89eea48d3de
-        env:
-          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
-
-  build:
-    needs: [coverage, lint]
-    name: Build
-    env:
-      CI: true
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ubuntu-latest]
-        node-version: [20.x]
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-
-      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061
-        name: Install pnpm
-        with:
-          run_install: false
-          package_json_file: "package.json"
-
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238
-        with:
-          node-version: ${{ matrix.node-version }}
-          cache: "pnpm"
-          cache-dependency-path: "pnpm-lock.yaml"
-
-      - name: Install Dependencies
-        shell: bash
-        run: pnpm install --frozen-lockfile
-
-      - name: Run build
-        env:
-          # We only want to upload bundle analysis for a PR once,
-          # so we only provide a token for the ubuntu-latest job.
-          CODECOV_TOKEN: ${{ matrix.os == 'ubuntu-latest' && secrets.CODECOV_TOKEN || '' }}
-        run: pnpm build

package/.github/workflows/release.yml

@@ -1,95 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-
-# This workflow will run changesets depending on two different scenarios:
-#
-# 1. If we are landing a specific commit into main (Author PR), then
-#    changesets will check if there are changes verifying the Markdown files
-#    generated automatically:
-#
-#    a) There are new versions and there's NO Release PR, then the changesets
-#    action will create a new Release PR.
-#
-#    b) There's a Release PR, then the changesets action will update the
-#    existing Release PR with the new commit.
-#
-#    NOTE: (in both cases, changesets will modify the new version in
-#    package.json for each package, and will remove the MD files as part of the
-#    Release PR).
-#
-# 2. If we are landing the Release PR into main, then the changesets action
-#    will publish the changes to npm.
-#
-# For more info about this workflow, see:
-# https://github.com/changesets/action#usage
-jobs:
-  release:
-    name: Release
-    runs-on: ubuntu-latest
-    permissions:
-      id-token: write # For provenance and trusted publishing
-      contents: write # For creating release PRs
-      pull-requests: write # For creating release PRs
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-
-      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061
-        name: Install pnpm
-        with:
-          run_install: false
-          package_json_file: package.json
-
-      - name: Use Node.js 20.x
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238
-        with:
-          node-version: 20.x
-          cache: pnpm
-          cache-dependency-path: pnpm-lock.yaml
-
-      - name: Install Dependencies
-        shell: bash
-        run: pnpm install --frozen-lockfile
-
-      - name: ⬆️ Upgrade npm for OIDC support
-        shell: bash
-        run: |
-          # npm trusted publishing requires npm CLI v11.5.1+
-          # Node.js 20 shipped with npm 9.x, so we likely need to upgrade
-
-          # First, let's check the current npm version, and if it's already
-          # sufficient, we can skip the upgrade step.
-          CURRENT_NPM_VERSION=$(npm --version)
-          REQUIRED_NPM_VERSION="11.5.1"
-
-          # This sorts the version numbers using `sort -V` and then takes
-          # the lowest version.
-          LOWEST_NPM_VERSION=$(printf '%s\n' "$REQUIRED_NPM_VERSION" "$CURRENT_NPM_VERSION" | sort -V | head -n1)
-
-          # If the lowest version is the same as the required version, then we
-          # don't need to upgrade as that means our current version is newer.
-          if [ "$LOWEST_NPM_VERSION" = "$REQUIRED_NPM_VERSION" ]; then
-            echo "✅ npm is already at version $CURRENT_NPM_VERSION"
-          else
-            npm install -g npm@latest && echo "✅ npm upgraded to $(npm --version)"
-          fi
-
-      - name: Create Release Pull Request or Publish to npm
-        id: changesets
-        uses: changesets/action@6a0a831ff30acef54f2c6aa1cbbc1096b066edaf
-        with:
-          publish: pnpm publish:ci
-        env:
-          # We use a Personal Access Token here rather than the GITHUB_TOKEN
-          # so that it will trigger our other actions. The token has to be on
-          # the account of someone with appropriate access levels and given the
-          # repo scope.
-          GITHUB_TOKEN: ${{ secrets.BOT_PA_TOKEN }}
-          # This is used for the bundle analysis
-          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

package/.vscode/settings.json

@@ -1,19 +0,0 @@
-{
-    "editor.formatOnSave": true,
-    "editor.defaultFormatter": "biomejs.biome",
-    "editor.codeActionsOnSave": {
-        "source.fixAll.biome": "explicit"
-    },
-    "[javascript]": {
-        "editor.defaultFormatter": "biomejs.biome"
-    },
-    "[typescript]": {
-        "editor.defaultFormatter": "biomejs.biome"
-    },
-    "[typescriptreact]": {
-        "editor.defaultFormatter": "biomejs.biome"
-    },
-    "[json]": {
-        "editor.defaultFormatter": "biomejs.biome"
-    }
-}

package/CHANGELOG.md

@@ -1,23 +0,0 @@
-# @somewhatabstract/x
-
-## 0.1.0
-
-### Minor Changes
-
-- 2f64864: Implement monorepo script execution tool with multi-package-manager support
-
-  - Add support for npm, Yarn, pnpm, Lerna, Bun, and Rush workspaces
-  - Implement direct script execution without interpreter detection
-  - Add dry-run mode for previewing execution
-  - Comprehensive test coverage
-
-- 2f64864: Support Node-executable script files (.js, .mjs, .cjs)
-
-  Bin scripts with `.js`, `.mjs`, or `.cjs` extensions are now automatically
-  invoked via the Node executable, matching npm/pnpm behavior. Previously, only
-  files with a shebang and executable permissions were supported.
-
-### Patch Changes
-
-- 2f64864: Add test coverage for all source files including the CLI entry point
-- 2f64864: Add Biome for linting and code formatting.

package/CODE_OF_CONDUCT.md

@@ -1,76 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at jeff[at]somewhatabstract[dot]com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq

package/CONTRIBUTING.md

@@ -1,70 +0,0 @@
-# Contributing to `x`
-
-🙇Thank you for your interest in contributing to this 📦.
-
-Whether raising an issue, reviewing a pull request, or implementing a change, the participation of others is a wonderful 🎁. Read on to find out how you can get involved.
-
-📖 Be sure to read our [Code of Conduct](CODE_OF_CONDUCT.md).
-
-## 🛑 Bugs And Feature Requests
-
-If you find a bug or want to make enhancements to the project, head on over to the [🔗Issues](https://github.com/somewhatabstract/x/issues) section and raise an issue. The issue templates will guide you in providing details that will help others help you.
-
-## 💻 Code Changes
-
-### ⓵ Making your first change
-
-Look for bugs or feature requests with the [good first issue](https://github.com/somewhatabstract/x/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) or [help wanted](https://github.com/somewhatabstract/x/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+) labels and have a go at implementing a change. Once your change is ready, you can submit a pull request.
-
-### 🎬 Getting Started
-
-To work in the `x` repository, follow these steps:
-
-1. Clone the repository
-   - `gh repo clone somewhatabstract/x`
-   - -or-
-   - `git clone git@github.com:somewhatabstract/x.git`
-2. Install `pnpm`
-   - `corepack enable pnpm`
-   - `corepack prepare pnpm --activate`
-3. Run `pnpm install` (or `pnpm i`) to install the dependencies
-
-You can now work on `x`. We prefer [🔗Visual Studio Code](https://code.visualstudio.com/) as our development environment (it's cross-platform and awesome), but please use what you feel comfortable with (we'll even forgive you for using vim).
-
-### 🧪 Code Quality
-
-#### Manual
-
-We love code reviews. If there are open pull requests, please feel free to review them and provide feedback. Feedback is a gift and code reviews are often a bottleneck in getting new things released. Jump in, even if you don't know anything; you probably know more than you think.
-
-💭**REMEMBER** Be kind and considerate. Folks are volunteering their time and code reviews are a moment of vulnerability where a criticism of the code can easily become a criticism of the individual that wrote it.
-
-1. Take your time
-2. Consider how you might receive the feedback you are giving if it were attached to code you wrote
-3. Favor asking questions over prescribing solutions.
-
-#### Automated
-
-To ensure code quality, we use TypeScript, biome, and vitest. These are all executed when you submit a pull request to ensure contributions meet our code quality standards.
-
-To execute these operations outside of a pull request, you can use `pnpm`.
-
-- `pnpm typecheck`
-- `pnpm lint`
-- `pnpm test`
-
-If you make changes that change snapshots, you may need to run tests with the `-u` vitest option and commit the updated snapshot files along with the rest of your contribution.
-
-💭**REMEMBER** If you would like to contribute code changes to the project, first make sure there's a corresponding issue for the change you wish to make.
-
-## 📦 Build And Publish
-
-Anyone can create a local build of the distributed code by running `pnpm build`.
-
-Running the build will execute tests first.
-
-### Publishing
-
-Publishing is automated through our use of [changesets][1]. When a PR is merged to `main`, a release PR is created that bundles all the changes since the last release. When we are ready to release, this bundled PR is merged to `main` which triggers changesets to publish to npm via trusted publishing.
-
-[1]:https://github.com/changesets/changesets/blob/main/README.md#documentation