Add original code

.github/ISSUE_TEMPLATE/1-bug.yml

@@ -2,8 +2,8 @@
 # SPDX-License-Identifier: Apache-2.0
 name: Bug Report
 description: Report a reproducible bug
-title: '[Bug] '
-labels: ['bug']
+title: "[Bug] "
+labels: ["bug"]
 assignees: []
 
 body:

.github/ISSUE_TEMPLATE/2-feature.yml

@@ -2,8 +2,8 @@
 # SPDX-License-Identifier: Apache-2.0
 name: Feature Request
 description: Suggest a feature or improvement
-title: '[Feature] '
-labels: ['enhancement']
+title: "[Feature] "
+labels: ["enhancement"]
 assignees: []
 
 body:

.github/ISSUE_TEMPLATE/3-other.yml

@@ -2,8 +2,8 @@
 # SPDX-License-Identifier: Apache-2.0
 name: Other
 description: Use this for anything that doesn't fit the other templates
-title: '[Other] '
-labels: ['discussion']
+title: "[Other] "
+labels: ["discussion"]
 assignees: []
 
 body:

.github/workflows/code-PR_verify-fallback.yml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   unit-tests:
-    if: 'false'
+    if: "false"
     name: Code / Verify
     runs-on: ubuntu-24.04
     steps:

.github/workflows/pr-verify.yml

@@ -20,7 +20,7 @@ jobs:
           fetch-depth: 0
           ref: ${{ github.event.pull_request.head.sha || github.sha }}
 
-      - name: 'Run Repolinter'
+      - name: "Run Repolinter"
         uses: newrelic/repolinter-action@3f4448f855c351e9695b24524a4111c7847b84cb # v1.7.0
 
   reuse-compliance:

.github/workflows/push-verify.yml

@@ -8,7 +8,6 @@ on:
     # Run on the long-lived git-flow branches.
     branches: ["develop", "main"]
 
-
 jobs:
   scorecard-analysis:
     # remove once public
@@ -53,7 +52,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
 
-      - name: 'Run Repolinter'
+      - name: "Run Repolinter"
         uses: newrelic/repolinter-action@3f4448f855c351e9695b24524a4111c7847b84cb # v1.7.0
 
   reuse-compliance:

.gitignore

@@ -1,9 +1,44 @@
-node_modules/
-.npm/
+# dependencies
+/node_modules
+example/node_modules
+/.pnp
+.pnp.js
 
-dist/
-coverage/
-.nyc_output/
+# testing
+/coverage
 
-*.log
-.DS_Store
+# production build
+/build
+/dist
+example/build
+
+# environment files
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+# keep the example's source-map setting tracked so the demo starts cleanly
+!example/.env
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
+
+# caches
+.eslintcache
+.cache
+.parcel-cache
+
+# editor / IDE
+.vscode/*
+!.vscode/settings.json
+!.vscode/extensions.json
+.idea
+
+# OS files
+.DS_Store
+Thumbs.db

.prettierignore

@@ -0,0 +1,4 @@
+dist
+node_modules
+example
+package-lock.json

.prettierrc

@@ -0,0 +1,3 @@
+{
+  "trailingComma": "es5"
+}

CHANGELOG.md

@@ -16,3 +16,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - Initial OSS repository shell.
+- Original code, including the diff highlighting plugin, and the example React application.

CONTRIBUTING.md

@@ -36,16 +36,16 @@ requests must include a `release-type/...` label unless the release is intention
 ## Contribution Guidelines
 
 - All contributors are expected to follow the project's [code of conduct](CODE_OF_CONDUCT.md). Please be respectful and
-considerate towards other contributors.
+  considerate towards other contributors.
 - Before starting work on a new feature or fix, check existing [issues](../../issues) and [pull requests](../../pulls)
-to avoid duplications and unnecessary discussions.
+  to avoid duplications and unnecessary discussions.
 - If you wish to work on an existing issue, comment on the issue to inform other contributors that you are working on it.
-This will help coordinate efforts and prevent conflicts.
+  This will help coordinate efforts and prevent conflicts.
 - It is always advisable to discuss and gather feedback from the community before making significant changes to the
-project's structure or architecture.
+  project's structure or architecture.
 - Ensure a clean and organized commit history. Divide your changes into logical and descriptive commits. We recommend to use the [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/)
 - Document any new changes or features you add. This will help other contributors and project users understand your work
-and its purpose.
+  and its purpose.
 - Be sure to link the corresponding issue in your pull request to maintain proper tracking of contributions.
 - Remember to add license and copyright information following the [REUSE Specification](https://reuse.software/spec/#copyright-and-licensing-information).