@ic-reactor/mcp 0.0.0-stage → 0.0.0

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,108 @@
+name: 🐛 Bug Report
+description: Report a bug or unexpected behavior
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please provide as much detail as possible.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Pre-submission Checklist
+      options:
+        - label: I have searched the [existing issues](https://github.com/B3Pay/ic-reactor/issues) to make sure this bug hasn't been reported before
+          required: true
+        - label: I am using the latest version of the package
+          required: true
+
+  - type: dropdown
+    id: package
+    attributes:
+      label: Which package(s) are affected?
+      multiple: true
+      options:
+        - "@ic-reactor/core"
+        - "@ic-reactor/react"
+        - "@ic-reactor/vite-plugin"
+        - "@ic-reactor/mcp"
+        - "@ic-reactor/candid (3.x)"
+        - "@ic-reactor/parser, codegen or cli (3.x)"
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Package Version
+      description: What version of the package are you using?
+      placeholder: "4.0.0"
+    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: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior
+      placeholder: |
+        1. Install package with '...'
+        2. Create component with '...'
+        3. Call function '...'
+        4. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: A clear description of what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: A clear description of what actually happened.
+    validations:
+      required: true
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Code Example
+      description: If applicable, provide a minimal code example that reproduces the issue.
+      render: typescript
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: |
+        Please provide your environment details:
+      value: |
+        - OS: [e.g., macOS 14.0, Ubuntu 22.04]
+        - Node.js: [e.g., 22.12.0]
+        - Package Manager: [e.g., pnpm 9.0.0]
+        - Browser (if applicable): [e.g., Chrome 120]
+        - Framework (if applicable): [e.g., React 18, Next.js 14]
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Add any other context, screenshots, or error logs about the problem here.

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: 🔒 Report a security vulnerability
+    url: https://github.com/B3Pay/ic-reactor/security/advisories/new
+    about: Report it privately, as SECURITY.md asks, and not in a public issue.
+  - name: 📖 Documentation
+    url: https://b3pay.net/docs/ic-reactor/
+    about: Guides, examples and the API reference of ic-reactor 4.

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,77 @@
+name: ✨ Feature Request
+description: Suggest a new feature or enhancement
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a feature! Please provide as much detail as possible.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Pre-submission Checklist
+      options:
+        - label: I have searched the [existing issues](https://github.com/B3Pay/ic-reactor/issues) to make sure this feature hasn't been requested before
+          required: true
+
+  - type: dropdown
+    id: package
+    attributes:
+      label: Which package(s) would this feature affect?
+      multiple: true
+      options:
+        - "@ic-reactor/core"
+        - "@ic-reactor/react"
+        - "@ic-reactor/vite-plugin"
+        - "@ic-reactor/mcp"
+        - "New package"
+        - "Documentation"
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: A clear description of the problem this feature would solve. What limitation or pain point are you experiencing?
+      placeholder: "I'm always frustrated when..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the solution you'd like to see implemented.
+    validations:
+      required: true
+
+  - type: textarea
+    id: api
+    attributes:
+      label: Suggested API (if applicable)
+      description: If you have ideas about what the API might look like, share them here.
+      render: typescript
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Have you considered any alternative solutions or workarounds?
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: How important is this feature to you?
+      options:
+        - "Nice to have"
+        - "Important, but I can work around it"
+        - "Critical for my use case"
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      options:
+        - label: I would be willing to submit a PR to implement this feature

package/.github/actions/setup-rust-wasm/action.yml

@@ -0,0 +1,25 @@
+name: "Setup Rust for the e2e canister build"
+description: >-
+  Installs the stable Rust toolchain with the wasm32-unknown-unknown target and
+  restores the cargo cache of the e2e hello_actor canister, which `icp deploy`
+  builds in e2e.yml. On the v4 line no package build needs Rust; the parser's
+  wasm-pack build that used to share this action is deleted there.
+
+runs:
+  using: composite
+  steps:
+    - name: Install Rust
+      uses: dtolnay/rust-toolchain@4cda84d5c5c54efe2404f9d843567869ab1699d4 # stable
+      with:
+        targets: wasm32-unknown-unknown
+
+    - name: Cache Rust dependencies
+      uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
+      with:
+        path: |
+          ~/.cargo/registry
+          ~/.cargo/git
+          e2e/target
+        key: ${{ runner.os }}-cargo-${{ hashFiles('e2e/Cargo.lock') }}
+        restore-keys: |
+          ${{ runner.os }}-cargo-

package/.github/dependabot.yml

@@ -0,0 +1,107 @@
+version: 2
+
+updates:
+  # Maintain dependencies for npm packages
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 10
+    groups:
+      # Group minor and patch updates together
+      dependencies:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
+      # Keep major updates separate for careful review
+      major:
+        patterns:
+          - "*"
+        update-types:
+          - "major"
+    ignore:
+      # TypeScript 7 is the native Go port, and its npm package does not ship the
+      # compiler API (`exports["."]` is `lib/version.cjs`; `ts.createProgram` is
+      # undefined). `tsup --dts` crashes inside rollup-plugin-dts, which breaks the
+      # vite-plugin build. The type system itself is ready -- tsc 7 checks every
+      # package with zero errors -- so this unblocks once vite-plugin moves off
+      # `tsup --dts`, or tsup gains TS7 support. See #225.
+      - dependency-name: "typescript"
+        update-types: ["version-update:semver-major"]
+      # stack.json chooses the Meant release, and `pnpm sync:stack` moves
+      # every pin together (CONTRIBUTING.md, "The Meant pins"). A bump of one
+      # package.json would fail `pnpm check:stack`, and in the grouped pull
+      # request it would hold back every other bump with it.
+      - dependency-name: "@meantjs/schema"
+      - dependency-name: "@meantjs/cli"
+    commit-message:
+      prefix: "deps"
+    labels:
+      - "dependencies"
+      - "automated"
+
+  # Rust crates of the e2e hello_actor canister. packages/parser, which this
+  # entry used to cover, is on the v3 branch only. Dependabot reads this file
+  # from the default branch (main) and opens pull requests against main only:
+  # the v3 branch gets no Dependabot pull requests, and its dependency-review
+  # job's audit is its advisory check.
+  - package-ecosystem: "cargo"
+    directory: "/e2e"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    groups:
+      cargo:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
+    commit-message:
+      prefix: "deps(e2e)"
+    labels:
+      - "dependencies"
+      - "automated"
+
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    groups:
+      # CodeQL's init, autobuild and analyze steps must run the same release.
+      # Dependabot names each path as its own dependency, so without this group
+      # it opens three PRs, and each one fails its CodeQL check with "Loaded a
+      # configuration file for version X, but running version Y". #323 and #375
+      # had to replace such a trio by hand.
+      codeql-action:
+        patterns:
+          - "github/codeql-action*"
+    commit-message:
+      prefix: "ci"
+    labels:
+      - "ci"
+      - "automated"
+
+  # The `github-actions` entry above uses `directory: "/"`, which covers
+  # `.github/workflows/**` but does NOT descend into `.github/actions/**`.
+  # Without this entry the two SHAs inside the setup-rust-wasm composite would be
+  # the only unmaintained action pins in a repo whose convention is that every
+  # action is SHA-pinned.
+  - package-ecosystem: "github-actions"
+    directory: "/.github/actions/setup-rust-wasm"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "ci"
+    labels:
+      - "ci"
+      - "automated"

package/.github/workflows/auth-latest.yml

@@ -0,0 +1,67 @@
+name: Auth on the latest @icp-sdk/auth
+
+# `auth: (network) => new AuthClient(network)` compiles only while
+# @icp-sdk/auth's AuthClient is an AuthLike. Core's dev dependency and the
+# examples pin @icp-sdk/auth ^10, so CI never sees a release outside that
+# range. This installs the newest release npm calls `latest`, type-checks core
+# (whose client.test-d.ts asserts AuthClient extends AuthLike) and runs the
+# core and react tests against it. Weekly, because @icp-sdk/auth releases with
+# no commit of ours. GitHub runs `schedule` and offers `workflow_dispatch` only
+# for workflow files on the default branch, main; a pull request that changes
+# this file runs it too.
+on:
+  pull_request:
+    branches: [main]
+    paths:
+      - ".github/workflows/auth-latest.yml"
+  workflow_dispatch:
+  schedule:
+    # Wednesdays, 06:41 UTC.
+    - cron: "41 6 * * 3"
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  auth-latest:
+    name: AuthLike against @icp-sdk/auth@latest
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - name: Checkout
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+
+      - name: Setup Node.js
+        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+        with:
+          node-version: 22
+
+      - name: Setup pnpm
+        run: |
+          corepack enable
+          corepack prepare pnpm@10.30.3 --activate
+          pnpm --version
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile --filter '!./examples/**'
+
+      # Not frozen: this is the one place the lockfile is meant to move.
+      - name: Install @icp-sdk/auth@latest into core
+        run: |
+          pnpm --filter @ic-reactor/core add --save-dev @icp-sdk/auth@latest
+          node -p "'@icp-sdk/auth ' + require('./packages/core/node_modules/@icp-sdk/auth/package.json').version"
+
+      - name: Build packages
+        run: pnpm build
+
+      - name: Type check core against it
+        run: pnpm --filter @ic-reactor/core typecheck
+
+      - name: Core and react tests against it
+        run: |
+          pnpm --filter @ic-reactor/core test
+          pnpm --filter @ic-reactor/react test

package/.github/workflows/b3pay-site.yml

@@ -0,0 +1,49 @@
+# Publishes these docs to b3pay.net, where they are served at
+# https://b3pay.net/docs/ic-reactor/: the pages of docs/src/content/docs, the
+# API reference TypeDoc generates, and packages/core/llms.txt, as
+# b3pay-module.json describes. b3pay.net's reusable workflow builds and checks
+# the module, then builds the whole site with it, so a page that would break
+# the site fails here. On main it also commits the built module to this
+# repository's b3pay-site branch, which b3pay.net serves, and asks b3pay.net
+# to rebuild. It never writes to b3pay.net.
+name: Docs on b3pay.net
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "docs/**"
+      - "packages/core/src/**"
+      - "packages/react/src/**"
+      - "packages/core/llms.txt"
+      - "pnpm-lock.yaml"
+      - "b3pay-module.json"
+      - ".github/workflows/b3pay-site.yml"
+  pull_request:
+    paths:
+      - "docs/**"
+      - "packages/core/src/**"
+      - "packages/react/src/**"
+      - "packages/core/llms.txt"
+      - "pnpm-lock.yaml"
+      - "b3pay-module.json"
+      - ".github/workflows/b3pay-site.yml"
+  workflow_dispatch:
+
+permissions: {}
+
+jobs:
+  module:
+    name: Docs module
+    # A commit of B3Pay/b3pay.net, not a branch: the publish job holds a token
+    # that can push to this repository.
+    uses: B3Pay/b3pay.net/.github/workflows/publish-module.yml@67911ef22a3d47012b285a8880375231ed79a526
+    with:
+      # Only main publishes: a pull request, or a manual run on another
+      # branch, only checks.
+      publish: ${{ github.ref == 'refs/heads/main' }}
+      prepare: corepack enable && pnpm install --frozen-lockfile && pnpm -C docs run api
+    permissions:
+      contents: write
+    secrets:
+      deploy-hook: ${{ secrets.B3PAY_SITE_DEPLOY_HOOK }}