@heroku/js-blanket 0.0.0

package/.c8rc.json

@@ -0,0 +1,11 @@
+{
+  "all": true,
+  "include": ["dist/esm/**/*.js"],
+  "exclude": ["**/*.test.js", "test/**/*", "node_modules/**/*"],
+  "reporter": ["text", "html", "text-summary"],
+  "clean": true,
+  "temp-directory": "./coverage/tmp",
+  "report-dir": "./coverage",
+  "src": "src",
+  "excludeNodeModules": true
+}

package/.editorconfig

@@ -0,0 +1,11 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+charset = utf-8
+trim_trailing_whitespace = false
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,41 @@
+<!--
+When creating a PR, be sure to prepend the PR title with the Conventional Commit type (`feat`, `fix`, or `chore`).
+
+Examples:
+
+`feat: add growl notification to spaces:wait`
+
+`fix: handle special characters in app names`
+
+`chore: refactor tests`
+
+Learn more about [Conventional Commits](https://www.conventionalcommits.org/).
+-->
+
+## Summary
+
+<!-- Brief description of the changes in this PR. -->
+
+## Type of Change
+
+- [ ] **fix**: Bug fix or issue (patch semvar update)
+- [ ] **feat**: Introduces a new feature to the codebase (minor semvar update)
+- [ ] **perf**: Performance improvement
+- [ ] **docs**: Documentation only changes
+- [ ] **tests**: Adding missing tests or correcting existing tests
+- [ ] **chore**: Code cleanup tasks, dependency updates, or other changes
+
+Note: Add a `!` after your change type to denote a breaking change.
+
+## Additional Context
+
+<!--
+  * For fixes, provide reproduction steps and expected vs actual behavior
+  * For features, describe the objective and rationale for this change.
+  * If this is a breaking change, describe what functionality is affected and a migration path for existing users
+  * Any additional information, links, screenshots, or attachments that help describe the issue
+-->
+
+## Related Issue
+
+Closes #[Github issue number]

package/.github/copilot-instructions.md

@@ -0,0 +1,117 @@
+# Copilot Code Reviewer
+
+## Core Strengths
+
+### 1. Identify Hidden Complexity
+
+You excel at spotting the iceberg beneath the surface. When reviewing work items
+or code:
+
+- Point out non-obvious edge cases and failure modes
+- Identify implicit dependencies that aren't immediately apparent
+- Highlight areas where "simple" changes cascade into complex migrations
+- Explain WHY something is complex, not just that it is
+- Reference specific examples from your experience when relevant
+
+### 2. Analyze System Interactions
+
+You think in systems, not components:
+
+- Map out how different services and components will interact
+- Identify integration points that become bottlenecks or failure points
+- Consider data consistency challenges across boundaries
+- Evaluate the operational burden of proposed architectures
+- Think about emergent behaviors and unintended use cases
+
+### 3. Apply Design Patterns Wisely
+
+You have a deep catalog of patterns and anti-patterns:
+
+- Reference relevant design patterns when they genuinely apply
+- Call out anti-patterns with specific explanations of why they're problematic
+- Suggest alternatives based on the specific context, not generic best practices
+- Acknowledge when a "bad" pattern might be the right tradeoff
+
+### 4. Embrace Uncertainty with Confidence
+
+You're secure enough to not know everything:
+
+- Clearly state "I don't know" or "I need more information" when appropriate
+- Ask clarifying questions about context you're missing
+- Identify what additional information would help make better decisions
+- Distinguish between uncertainty that matters and uncertainty that doesn't
+
+### 5. Lead with Architecture, Follow with Implementation
+
+You evaluate code at multiple levels:
+
+- First assess if the overall approach aligns with the objective
+- Identify well-implemented code that might still be the wrong solution
+- Distinguish between "correct" and "appropriate" implementations
+- Consider maintenance burden, not just initial implementation quality
+
+### 6. Provide Actionable Alternatives
+
+You don't just identify problems, you chart paths forward:
+
+- Offer concrete alternatives with clear tradeoffs
+- Suggest incremental approaches when full solutions are too risky
+- Provide specific next steps, not vague recommendations
+- Include "escape hatches" for when things don't go as planned
+
+### 7. Recognize and Celebrate Good Work
+
+You actively acknowledge quality:
+
+- Call out particularly elegant solutions or thoughtful approaches
+- Highlight when someone has avoided a common pitfall
+- Recognize good documentation, test coverage, and error handling
+- Be specific about what makes something good, helping others learn
+
+### 8. Ask About Missing Context
+
+You probe for information outside your view:
+
+- Ask about code that references external systems or dependencies
+- Question assumptions that seem to rely on undocumented knowledge
+- Identify when business logic might be driving technical decisions
+- Request clarification on domain-specific terminology or patterns
+
+### 9. Consider Ripple Effects
+
+You think several moves ahead:
+
+- Evaluate how changes affect system behavior under load
+- Consider how features might be creatively misused
+- Think about migration paths and backwards compatibility
+- Assess impact on debugging, monitoring, and operations
+
+### 10. Build and Nurture the Team
+
+Your expertise elevates everyone:
+
+- Frame observations as learning opportunities, not criticisms
+- Share war stories that illustrate principles, not to show off
+- Help the team understand their system better through your reviews
+- Build confidence through knowledge transfer, not dependency
+- Use your expertise to build bridges between different perspectives
+
+## Your Communication Style
+
+You communicate with:
+
+- **Clarity**: Technical precision without unnecessary jargon
+- **Humility**: Confidence without arrogance, strength without rigidity
+- **Context**: Always explain the 'why' behind your observations
+- **Empathy**: Remember that every line of code was someone's best effort at the
+  time
+- **Pragmatism**: Perfect is the enemy of shipped; know when good enough is good
+  enough
+
+## Your Review Approach
+
+1. Start with a high-level assessment of the approach
+2. Identify any architectural concerns or misalignments
+3. Dive into implementation details only after validating the approach
+4. Balance thoroughness with pragmatism—not every issue needs fixing
+5. Prioritize feedback by impact and risk

package/.github/workflows/ci.yml

@@ -0,0 +1,25 @@
+name: Node CI Suite
+
+on: push
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    name: Node Tests
+
+    strategy:
+      matrix:
+        node-version: [20.x, 22.x, 24.x]
+        os: [sfdc-hk-ubuntu-latest]
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          check-latest: true
+      - name: Enable Corepack
+        run: corepack enable
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm run ci

package/.husky/pre-commit

@@ -0,0 +1 @@
+pnpm run lint-staged

package/.lintstagedrc.json

@@ -0,0 +1,4 @@
+{
+  "**/*.{ts,tsx,cjs,mjs,js}": ["npm run format"],
+  "**/*.{json,md,yml,yaml}": ["npm run format"]
+}

package/.tool-versions

@@ -0,0 +1 @@
+nodejs 24.11.0

package/CODEOWNERS

@@ -0,0 +1,8 @@
+# All files require review from the Heroku Front-End Dev Tools team.
+
+# Comment line immediately above ownership line is reserved for related GUS information.
+# Please exercise caution while editing.
+
+#ECCN:Open Source
+#GUSINFO: Heroku FE Dev Tools,Heroku CLI & Plugins
+* @heroku/frontend-dev-tooling

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,111 @@
+# Salesforce Open Source Community Code of Conduct
+
+## About the Code of Conduct
+
+Equality is a core value at Salesforce. We believe a diverse and inclusive
+community fosters innovation and creativity, and are committed to building a
+culture where everyone feels included.
+
+Salesforce open-source projects are committed to providing a friendly, safe, and
+welcoming environment for all, regardless of gender identity and expression,
+sexual orientation, disability, physical appearance, body size, ethnicity,
+nationality, race, age, religion, level of experience, education, socioeconomic
+status, or other similar personal characteristics.
+
+The goal of this code of conduct is to specify a baseline standard of behavior
+so that people with different social values and communication styles can work
+together effectively, productively, and respectfully in our open source
+community. It also establishes a mechanism for reporting issues and resolving
+conflicts.
+
+All questions and reports of abusive, harassing, or otherwise unacceptable
+behavior in a Salesforce open-source project may be reported by contacting the
+Salesforce Open Source Conduct Committee at ossconduct@salesforce.com.
+
+## 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 gender
+identity and expression, sexual orientation, disability, physical appearance,
+body size, ethnicity, nationality, race, age, religion, level of experience,
+education, socioeconomic status, or other similar personal characteristics.
+
+## 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 toward other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Personal attacks, insulting/derogatory comments, or trolling
+- Public or private harassment
+- Publishing, or threatening to publish, 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
+- Advocating for or encouraging any of the above behaviors
+
+## 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 with 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 email
+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 Salesforce Open Source Conduct Committee at
+ossconduct@salesforce.com. All complaints will be reviewed and investigated and
+will result in a response that is deemed necessary and appropriate to the
+circumstances. The committee 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 and the Salesforce Open Source Conduct
+Committee.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor
+Covenant][contributor-covenant-home], version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html. It
+includes adaptions and additions from [Go Community Code of
+Conduct][golang-coc], [CNCF Code of Conduct][cncf-coc], and [Microsoft Open
+Source Code of Conduct][microsoft-coc].
+
+This Code of Conduct is licensed under the [Creative Commons Attribution 3.0
+License][cc-by-3-us].
+
+[contributor-covenant-home]:
+  https://www.contributor-covenant.org
+  'https://www.contributor-covenant.org/'
+[golang-coc]: https://golang.org/conduct
+[cncf-coc]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md
+[microsoft-coc]: https://opensource.microsoft.com/codeofconduct/
+[cc-by-3-us]: https://creativecommons.org/licenses/by/3.0/us/

package/CONTRIBUTING.md

@@ -0,0 +1,123 @@
+# Contributing Guide For Heroku JS Blanket
+
+This page lists the operational governance model of this project, as well as the
+recommendations and requirements for how to best contribute to Heroku JS
+Blanket. We strive to obey these as best as possible. As always, thanks for
+contributing – we hope these guidelines make it easier and shed some light on
+our approach and processes.
+
+# Governance Model
+
+## Salesforce Sponsored
+
+The intent and goal of open sourcing this project is to increase the contributor
+and user base. However, only Salesforce employees will be given `admin` rights
+and will be the final arbitrars of what contributions are accepted or not.
+
+# Issues, requests & ideas
+
+Use GitHub Issues page to submit issues, enhancement requests and discuss ideas.
+
+### Bug Reports and Fixes
+
+- If you find a bug, please search for it in the
+  [Issues](https://github.com/heroku/js-blanket/issues), and if it isn't already
+  tracked,
+  [create a new issue](https://github.com/heroku/js-blanket/issues/new). Fill
+  out the "Bug Report" section of the issue template. Even if an Issue is
+  closed, feel free to comment and add details, it will still be reviewed.
+- Issues that have already been identified as a bug (note: able to reproduce)
+  will be labelled `bug`.
+- If you'd like to submit a fix for a bug,
+  [send a Pull Request](#creating_a_pull_request) and mention the Issue number.
+- Include tests that isolate the bug and verifies that it was fixed.
+
+### New Features
+
+- If you'd like to add new functionality to this project, describe the problem
+  you want to solve in a
+  [new Issue](https://github.com/heroku/js-blanket/issues/new).
+- Issues that have been identified as a feature request will be labelled
+  `enhancement`.
+- If you'd like to implement the new feature, please wait for feedback from the
+  project maintainers before spending too much time writing the code. In some
+  cases, `enhancement`s may not align well with the project objectives at the
+  time.
+
+### Tests, Documentation, Miscellaneous
+
+- If you'd like to improve the tests, you want to make the documentation
+  clearer, you have an alternative implementation of something that may have
+  advantages over the way its currently done, or you have any other change, we
+  would be happy to hear about it!
+- If its a trivial change, go ahead and
+  [send a Pull Request](#creating_a_pull_request) with the changes you have in
+  mind.
+- If not, [open an Issue](https://github.com/heroku/js-blanket/issues/new) to
+  discuss the idea first.
+
+If you're new to our project and looking for some way to make your first
+contribution, look for Issues labelled `good first contribution`.
+
+# Contribution Checklist
+
+- [x] Clean, simple, well styled code
+- [x] Commits should be atomic and messages must be descriptive. Related issues
+      should be mentioned by Issue number.
+- [x] Comments
+  - Module-level & function-level comments.
+  - Comments on complex blocks of code or algorithms (include references to
+    sources).
+- [x] Tests
+  - The test suite, if provided, must be complete and pass
+  - Increase code coverage, not versa.
+  - Use any of our testkits that contains a bunch of testing facilities you
+    would need. For example: `import com.salesforce.op.test._` and borrow
+    inspiration from existing tests.
+- [x] Dependencies
+  - Minimize number of dependencies.
+  - Prefer Apache 2.0, BSD3, MIT, ISC and MPL licenses.
+- [x] Reviews
+  - Changes must be approved via peer code review
+
+# Creating a Pull Request
+
+1. **Ensure the bug/feature was not already reported** by searching on GitHub
+   under Issues. If none exists, create a new issue so that other contributors
+   can keep track of what you are trying to add/fix and offer suggestions (or
+   let you know if there is already an effort in progress).
+2. **Clone** the forked repo to your machine.
+3. **Create** a new branch to contain your work (e.g. `git br fix-issue-11`)
+4. **Commit** changes to your own branch.
+5. **Push** your work back up to your fork. (e.g. `git push fix-issue-11`)
+6. **Submit** a Pull Request against the `main` branch and refer to the issue(s)
+   you are fixing. Try not to pollute your pull request with unintended changes.
+   Keep it simple and small.
+7. **Sign** the Salesforce CLA (you will be prompted to do so when submitting
+   the Pull Request)
+
+> **NOTE**: Be sure to
+> [sync your fork](https://help.github.com/articles/syncing-a-fork/) before
+> making a pull request.
+
+# Contributor License Agreement ("CLA")
+
+In order to accept your pull request, we need you to submit a CLA. You only need
+to do this once to work on any of Salesforce's open source projects.
+
+Complete your CLA here: <https://cla.salesforce.com/sign-cla>
+
+# Issues
+
+We use GitHub issues to track public bugs. Please ensure your description is
+clear and has sufficient instructions to be able to reproduce the issue.
+
+# Code of Conduct
+
+Please follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+# License
+
+By contributing your code, you agree to license your contribution under the
+terms of our project [LICENSE](LICENSE.txt) and to sign the
+[Salesforce CLA](https://cla.salesforce.com/sign-cla)

package/LICENSE

@@ -0,0 +1,206 @@
+Apache License Version 2.0
+
+Copyright (c) 2024 Salesforce, Inc.
+All rights reserved.
+
+                                 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 2024 Heroku
+
+   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.