wrapture 0.0.1

package/.browserslistrc

@@ -0,0 +1,4 @@
+> 5%
+last 2 Firefox major versions
+Firefox ESR
+not dead

package/.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+

package/.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+
+github: phun-ky
+custom: ["https://www.paypal.me/phunky"]

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'problems: bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

package/.github/dependabot.yml

@@ -0,0 +1,25 @@
+version: 2
+updates:
+  - package-ecosystem: 'npm'
+    directory: '/'
+    groups:
+      minor-and-patch:
+        applies-to: version-updates
+        update-types:
+          - 'minor'
+          - 'patch'
+      major-updates:
+        applies-to: version-updates
+        update-types:
+          - 'major'
+    schedule:
+      interval: 'weekly'
+    labels:
+      - 'mindless: 📦 dependencies'
+      - 'problems: security'
+    commit-message:
+      prefix: 'chore: 🤖 '
+    open-pull-requests-limit: 2
+    allow:
+      - dependency-type: direct
+      - dependency-type: production

package/.github/labeler.yml

@@ -0,0 +1,72 @@
+'section: workflows':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - .github/workflows/**
+'section: repo':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - '*'
+'experience: developer':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - '.editorconfig'
+              - '.eslintignore'
+              - '.eslintrc.json'
+              - '.eslintrc.js'
+              - '.gitignore'
+              - '.release-it.json'
+              - '.renovate.json'
+              - '.npmrc'
+              - '.prettierrc'
+'context: github':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - .github/**
+'context: docker':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - Dockerfile
+'context: npm':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - '.npmrc'
+'context: rollup':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - 'rollup.config.js'
+              - 'rollup.config.mjs'
+              - 'rollup.*.config.js'
+              - 'rollup.*.config.mjs'
+'mindless: ✏️ docs':
+  - any:
+      - head-branch: ['^docs', 'docs']
+      - changed-files:
+          - any-glob-to-any-file:
+              - '**/*.md'
+'mindless: dependencies':
+  - any:
+      - changed-files:
+          - any-glob-to-any-file:
+              - 'package-lock.json'
+              - 'yarn.lock'
+
+# Add '✨ feature' label to any PR where the head branch name starts with `feat` or has a `feat` section in the name
+'✨ feature':
+  - head-branch: ['^feat', 'feat']
+'problems: 🐛 bug':
+  - head-branch: ['^fix', 'fix']
+'mindless: 🤖 chore':
+  - head-branch: ['^chore', 'chore']
+'improvements: 💡 enhancement':
+  - head-branch: ['^improvements', 'improvements']
+
+# Add 'release' label to any PR that is opened against the `main` branch
+release:
+  - base-branch: 'main'

package/.github/labels.yml

@@ -0,0 +1,24 @@
+XS:
+  name: 'size: 👕 XS'
+  lines: 0
+  color: 3CBF00
+S:
+  name: 'size: 👕 S'
+  lines: 10
+  color: 5D9801
+M:
+  name: 'size: 👕 M'
+  lines: 30
+  color: 7F7203
+L:
+  name: 'size: 👕 L'
+  lines: 100
+  color: A14C05
+XL:
+  name: 'size: 👕 XL'
+  lines: 500
+  color: C32607
+XXL:
+  name: 'size: 👕 XXL'
+  lines: 1000
+  color: E50009

package/.github/workflows/auto-assign.yml

@@ -0,0 +1,19 @@
+name: Auto Assign
+on:
+  issues:
+    types: [opened]
+  pull_request:
+    types: [opened]
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+    - name: 'Auto-assign issue'
+      uses: pozil/auto-assign-issue@v1
+      with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          assignees: phun-ky
+          numOfAssignee: 1

package/.github/workflows/check.yml

@@ -0,0 +1,72 @@
+# This is a basic workflow to help you get started with Actions
+
+name: Checks
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the "main" branch
+  push:
+    branches: ['main']
+    paths:
+      - '.github/**'
+      - 'src/**'
+      - 'package.json'
+      - 'package-lock.json'
+      - 'rollup.config.js'
+      - 'tsconfig.json'
+      - '.npmrc'
+  pull_request:
+    branches: ['main']
+    types: [opened, synchronize] # Workflow triggering events
+    paths:
+      - '.github/**'
+      - 'src/**'
+      - 'package.json'
+      - 'package-lock.json'
+      - 'rollup.config.js'
+      - 'tsconfig.json'
+      - '.npmrc'
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "check"
+  check:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # Checkout all branches and tags
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=22.8.0'
+      - name: Install dependencies
+        run: | # Install and link dependencies
+          npm i
+      - name: Build # Build all packages
+        run: npm run build
+      - name: Test
+        run: npm run test:ci
+      - name: Upload coverage reports to Codecov
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          slug: phun-ky/wrapture
+  notify:
+    name: Notify failed check
+    needs: check
+    if: failure()
+    runs-on: ubuntu-latest
+    steps:
+      - uses: jayqi/failed-build-issue-action@v1.2
+        with:
+          github-token: ${{ secrets.GH_TOKEN }}
+          label-name: 'problems: build failed'

package/.github/workflows/label.yml

@@ -0,0 +1,16 @@
+name: 'Pull Request Labeler'
+on:
+  - pull_request_target
+
+jobs:
+  labeler:
+    permissions:
+      contents: read
+      pull-requests: write
+      issues: write
+    runs-on: ubuntu-latest
+    steps:
+      - id: label-the-PR
+        uses: actions/labeler@v5
+        with:
+          sync-labels: true

package/.github/workflows/publish.yml

@@ -0,0 +1,66 @@
+# This is a basic workflow to help you get started with Actions
+
+name: Publish
+
+# Controls when the workflow will run
+on:
+  pull_request:
+    types: [closed]
+    branches: [ "main" ]
+    paths:
+      - '.github/**'
+      - 'src/**'
+      - 'api/**'
+      - 'public/**'
+      - 'package.json'
+      - 'package-lock.json'
+      - 'rollup.config.js'
+      - 'tsconfig.json'
+      - '.npmrc'
+      - '.release-it.json'
+      - 'README.md'
+      - 'CONTRIBUTING.md'
+      - 'CODE_OF_CONDUCT.md'
+      - 'SECURITY.md'
+      - '.postcssrc.cjs'
+      - '.browserlistrc'
+  workflow_dispatch:
+jobs:
+  publish:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # Checkout all branches and tags
+          token: ${{ secrets.GH_TOKEN }}
+      - name: Setup Node.js environment
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=22.8.0'
+      - name: Install dependencies
+        run: | # Install and link dependencies
+          npm i
+      - name: "Release" # Interesting step
+        run: |
+          git config user.name "${{ github.actor }}"
+          git config user.email "${{ github.actor}}@users.noreply.github.com"
+          npm run release
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
+  notify:
+    name: Notify failed build
+    needs: publish
+    if: failure()
+    runs-on: ubuntu-latest
+    steps:
+      - uses: jayqi/failed-build-issue-action@v1.2
+        with:
+          github-token: ${{ secrets.GH_TOKEN }}
+          label-name: "problems: build failed"
+

package/.github/workflows/triage.yml

@@ -0,0 +1,18 @@
+name: Add triage label
+on:
+  issues:
+    types:
+      - reopened
+      - opened
+jobs:
+  label_issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - run: gh issue edit "$NUMBER" --add-label "$LABELS"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}
+          LABELS: 🚑 triage

package/.markdownlint.json

@@ -0,0 +1,7 @@
+{
+  "MD013": {"code_blocks": false},
+  "MD033": false,
+  "MD036": false,
+  "MD040": false,
+  "MD046": {"style": "fenced"}
+}

package/.prettierrc

@@ -0,0 +1,7 @@
+{
+  "singleQuote": true,
+  "trailingComma": "none",
+  "tabWidth": 2,
+  "proseWrap": "always",
+  "printWidth": 80
+}

package/.release-it.json

@@ -0,0 +1,67 @@
+{
+  "git": {
+    "commitMessage": "chore: 🤖 release v${version}"
+  },
+  "github": {
+    "release": true,
+    "tokenRef": "GH_TOKEN"
+  },
+  "npm": {
+    "publish": true,
+    "skipChecks": true
+  },
+  "hooks": {
+    "after:bump": "npm run build && npm run docs:gen",
+    "after:release": "echo Successfully released ${name} v${version} to ${repo.repository}."
+  },
+  "plugins": {
+    "@release-it/conventional-changelog": {
+      "header": "# Changelog",
+      "preset": {
+        "name": "conventionalcommits",
+        "types": [
+          {
+            "type": "chore",
+            "section": "Tasks"
+          },
+          {
+            "type": "docs",
+            "section": "Documentation"
+          },
+          {
+            "type": "feat",
+            "section": "Feature"
+          },
+          {
+            "type": "fix",
+            "section": "Bug"
+          },
+          {
+            "type": "perf",
+            "section": "Performance change"
+          },
+          {
+            "type": "refactor",
+            "section": "Refactoring"
+          },
+          {
+            "type": "release",
+            "section": "Create a release commit",
+            "hidden": true
+          },
+          {
+            "type": "style",
+            "section": "Markup, white-space, formatting, missing semi-colons...",
+            "hidden": true
+          },
+          {
+            "type": "test",
+            "section": "Adding missing tests",
+            "hidden": true
+          }
+        ]
+      },
+      "infile": "CHANGELOG.md"
+    }
+  }
+}

package/CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+## 0.0.1 (2025-05-14)
+
+### Tasks
+
+* 🤖 bump putout from 40.1.8 to 40.1.9 in the minor-and-patch group ([259b0f2](https://github.com/phun-ky/wrapture/commit/259b0f28011274b097c7c534ec491437d51bf806))
+* 🤖 First code release ([63a78ae](https://github.com/phun-ky/wrapture/commit/63a78aefc3260e9d30918b90c1c460db53279310))

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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, 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 behaviour 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 behaviour 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 behaviour and will take appropriate and fair corrective action in
+response to any behaviour 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 e-mail 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 behaviour may be
+reported to the community leaders responsible for enforcement at
+<code-of-conduct@phun-ky.net>. 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 behaviour 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
+behaviour 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 behaviour. 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 behaviour.
+
+**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 behaviour, 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.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.