create yml for deployiING

[supervoidcoder]

create a yml workflow to deploy to pages

[supervoidcoder]

@coderabbitai please do this

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@supervoidcoder I'll help you create a GitHub Actions workflow to deploy to GitHub Pages. Let me first explore the repository structure to understand what kind of project this is and create an appropriate workflow.

---

🏁 Script executed:

#!/bin/bash

Explore the repository structure

echo "=== Repository structure ==="
ls -la

echo -e "\n=== Check for existing workflows ==="
ls -la .github/workflows/ 2>/dev/null || echo "No workflows directory found"

echo -e "\n=== Check for package.json ==="
cat package.json 2>/dev/null || echo "No package.json found"

echo -e "\n=== Check for requirements.txt ==="
cat requirements.txt 2>/dev/null || echo "No requirements.txt found"

echo -e "\n=== Check for README ==="
cat README.md 2>/dev/null || echo "No README.md found"

echo -e "\n=== Check file types in root ==="
fd -t f -d 1 -e html -e py -e js -e ts -e md

echo -e "\n=== Check for any build configuration ==="
ls -la | grep -E "vite|webpack|rollup|next|gatsby|jekyll|hugo|mkdocs|sphinx"

Length of output: 9916

---

🏁 Script executed:

#!/bin/bash

Check build configuration to find output directory

echo "=== Check build/build.js ==="
cat build/build.js | grep -A5 -B5 "dist|output"

echo -e "\n=== Check webpack config for output ==="
fd webpack.conf.js -t f --exec grep -l "output" {} ; | head -1 | xargs cat | grep -A10 "output:"

echo -e "\n=== Check for dist directory ==="
ls -la dist/ 2>/dev/null || echo "No dist directory found yet"

Length of output: 131

---

🏁 Script executed:

#!/bin/bash

Check build configuration files directly

echo "=== Full build/build.js content ==="
cat build/build.js

echo -e "\n=== Check config directory ==="
ls -la config/

echo -e "\n=== Check webpack config files ==="
fd webpack -t f -e js

Length of output: 1460

---

🏁 Script executed:

#!/bin/bash

Check config to find output directory

echo "=== Config index.js ==="
cat config/index.js

Length of output: 1487

---

@supervoidcoder Perfect! I've analyzed the repository structure. This is a Vue.js/webpack project (StackEdit) that builds to a `dist/` directory. I'll create a GitHub Actions workflow to deploy it to GitHub Pages.

---

🏁 Script executed:

#!/bin/bash
# Create the .github/workflows directory and the deploy workflow
mkdir -p .github/workflows

# Create the GitHub Pages deployment workflow
cat > .github/workflows/deploy-pages.yml << 'EOF'
name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4
EOF

echo "Workflow file created successfully!"
cat .github/workflows/deploy-pages.yml

Length of output: 1337

---

---

🏁 Script executed:

#!/bin/bash

Update the GitHub issue with the workflow details

gh issue comment 1 --body "✅ GitHub Pages Deployment Workflow Created

I've created a GitHub Actions workflow file at `.github/workflows/deploy-pages.yml` that will automatically deploy your StackEdit application to GitHub Pages.

📋 What the workflow does:

1. Triggers on:

   • Push to `main` or `master` branch
   • Manual workflow dispatch

2. Build job:

   • Checks out the code
   • Sets up Node.js 16
   • Installs dependencies with `npm ci`
   • Runs `npm run build` to build the project
   • Uploads the `dist/` directory as a Pages artifact

3. Deploy job:

   • Deploys the artifact to GitHub Pages

⚙️ Configuration Required:

To enable GitHub Pages deployment, you need to configure your repository settings:

1. Go to your repository Settings → Pages
2. Under Source, select GitHub Actions
3. Save the changes

🚀 Usage:

Once configured, the workflow will automatically run on every push to the main branch. You can also trigger it manually from the Actions tab.

Your site will be available at: `https://omniblocks.github.io/NotebookWriter/\`

The workflow file is ready to be committed to your repository!"

Length of output: 60

---



</details>

@supervoidcoder ✅ I've created a GitHub Actions workflow to deploy your StackEdit application to GitHub Pages!

## 📄 Workflow File Created

The workflow file is at `.github/workflows/deploy-pages.yml`:

```yaml
name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

⚙️ Configuration Required

Before the workflow can deploy, you need to enable GitHub Pages in your repository settings:

1. Go to Settings → Pages in your repository
2. Under Source, select GitHub Actions
3. Save the changes

🚀 How It Works

• Automatic deployment: Triggers on every push to main or master branch
• Manual deployment: Can be triggered manually from the Actions tab
• Build process: Installs dependencies, runs npm run build, and deploys the dist/ folder
• Your site will be available at: https://omniblocks.github.io/NotebookWriter/

The workflow file is ready to be committed and pushed to your repository! Once you push it and configure the Pages settings, your site will be automatically deployed.

[supervoidcoder]

@coderabbitai
Skip to content
Navigation Menu
OmniBlocks
NotebookWriter

Code
Issues 1
Pull requests
Actions
Projects
Models
Security
Insights

Settings

Deploy to GitHub Pages
Add GitHub Actions workflow for GitHub Pages deployment #1

Jobs

Run details

Annotations
1 error
build
failed 2 minutes ago in 55s
2s
2s
1s
1s
3s
3s
46s
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated osenv@0.1.4: This package is no longer supported.
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated mixin-deep@1.3.0: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated kleur@2.0.1: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <[https://github.com/lukeed/kleur/releases/tag/v3.0.0](https://github.com/lukeed/kleur/releases/tag/v3.0.0/)> for migration path(s).
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated har-validator@5.1.0: this library is no longer supported
npm WARN deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated eslint-loader@2.1.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net/ ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated are-we-there-yet@1.1.4: This package is no longer supported.
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated abab@2.0.0: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated vue@2.5.17: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated electron-releases@2.1.0: this package is no longer updated, please fetch version information from https://releases.electronjs.org/releases.json instead
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated core-js@2.5.3: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T22_51_18_190Z-debug-0.log
Error: Process completed with exit code 128.
46s
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated osenv@0.1.4: This package is no longer supported.
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated mixin-deep@1.3.0: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated kleur@2.0.1: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <[https://github.com/lukeed/kleur/releases/tag/v3.0.0](https://github.com/lukeed/kleur/releases/tag/v3.0.0/)> for migration path(s).
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated har-validator@5.1.0: this library is no longer supported
npm WARN deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated eslint-loader@2.1.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net/ ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated are-we-there-yet@1.1.4: This package is no longer supported.
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated abab@2.0.0: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated vue@2.5.17: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated electron-releases@2.1.0: this package is no longer updated, please fetch version information from https://releases.electronjs.org/releases.json instead
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated core-js@2.5.3: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T22_51_18_190Z-debug-0.log
Error: Process completed with exit code 128.
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated osenv@0.1.4: This package is no longer supported.
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated mixin-deep@1.3.0: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated kleur@2.0.1: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <[https://github.com/lukeed/kleur/releases/tag/v3.0.0](https://github.com/lukeed/kleur/releases/tag/v3.0.0/)> for migration path(s).
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated har-validator@5.1.0: this library is no longer supported
npm WARN deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated eslint-loader@2.1.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net/ ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated are-we-there-yet@1.1.4: This package is no longer supported.
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated abab@2.0.0: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated vue@2.5.17: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated electron-releases@2.1.0: this package is no longer updated, please fetch version information from https://releases.electronjs.org/releases.json instead
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated core-js@2.5.3: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T22_51_18_190Z-debug-0.log
46s
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated osenv@0.1.4: This package is no longer supported.
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated mixin-deep@1.3.0: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated kleur@2.0.1: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <[https://github.com/lukeed/kleur/releases/tag/v3.0.0](https://github.com/lukeed/kleur/releases/tag/v3.0.0/)> for migration path(s).
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated har-validator@5.1.0: this library is no longer supported
npm WARN deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated eslint-loader@2.1.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net/ ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated are-we-there-yet@1.1.4: This package is no longer supported.
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated abab@2.0.0: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated vue@2.5.17: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated electron-releases@2.1.0: this package is no longer updated, please fetch version information from https://releases.electronjs.org/releases.json instead
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated core-js@2.5.3: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T22_51_18_190Z-debug-0.log
Error: Process completed with exit code 128.
0s
0s
0s
0s
0s
0s
0s
0s
1s
1s
0s
0s
Add GitHub Actions workflow for GitHub Pages deployment · 027eede
Failed to load latest commit information.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check package.json for git SSH dependencies
echo "=== Checking package.json for git dependencies ==="
cat package.json | jq '.dependencies, .devDependencies' | grep -i "git" || echo "Using jq failed, trying grep"

echo -e "\n=== Raw search for MIDI.js in package.json ==="
grep -i "midi" package.json || echo "No MIDI references found"

echo -e "\n=== Full package.json content ==="
cat package.json

Length of output: 4951

---

🏁 Script executed:

#!/bin/bash
# Check if package-lock.json exists and search for MIDI references
echo "=== Searching for MIDI.js in package-lock.json ==="
if [ -f package-lock.json ]; then
  grep -i "midi" package-lock.json | head -20
else
  echo "No package-lock.json found"
fi

echo -e "\n=== Checking for yarn.lock ==="
if [ -f yarn.lock ]; then
  grep -i "midi" yarn.lock | head -20
else
  echo "No yarn.lock found"
fi

Length of output: 357

---

@supervoidcoder I found the issue! The build is failing because one of your dependencies (MIDI.js, which is a subdependency of the abcjs music notation library) is being accessed via SSH URL, but GitHub Actions doesn't have SSH keys configured.

Here's the updated workflow that will fix this problem:

---

🏁 Script executed:

#!/bin/bash
# Update the workflow to fix the SSH/HTTPS issue
cat > .github/workflows/deploy-pages.yml << 'EOF'
name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'
          cache: 'npm'

      - name: Configure git to use HTTPS instead of SSH
        run: git config --global url."https://github.com/".insteadOf ssh://git@github.com/

      - name: Install dependencies
        run: npm ci

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4
EOF

echo "Updated workflow file created!"
cat .github/workflows/deploy-pages.yml

Length of output: 1480

---

@supervoidcoder I've identified and fixed the issue! 🎯

🐛 The Problem

The build was failing because the abcjs package (for music notation) has a dependency on MIDI.js that npm was trying to fetch via SSH (ssh://git@github.com/paulrosen/MIDI.js.git). GitHub Actions runners don't have SSH keys configured, causing the "Permission denied (publickey)" error.

✅ The Solution

I've updated the workflow to include a git configuration step that automatically rewrites SSH URLs to HTTPS URLs. Here's what changed:

New step added before "Install dependencies":

- name: Configure git to use HTTPS instead of SSH
  run: git config --global url."https://github.com/".insteadOf ssh://git@github.com/

This command tells git to automatically convert any ssh://git@github.com/ URLs to https://github.com/ URLs, which don't require SSH keys.

📝 Next Steps

The updated workflow file has been created at .github/workflows/deploy-pages.yml. You need to:

1. Commit and push this updated workflow file to your repository
2. The workflow will automatically run and should now successfully build and deploy to GitHub Pages

Once pushed, you can monitor the workflow run in the Actions tab, and it should complete successfully this time! 🚀

Your site will be available at: https://omniblocks.github.io/NotebookWriter/

[supervoidcoder]

@coderabbitai
"
Navigation Menu
OmniBlocks
NotebookWriter

Code
Issues
1
Pull requests
Actions
Projects
Models
Security
Insights
Deploy to GitHub Pages
Update deploy.yml #2
Jobs
Run details
Annotations
1 error
build
failed 1 minute ago in 56s

2s
1s
3s
1s
Run git config --global url."https://github.com/".insteadOf ssh://git@github.com/
git config --global url."https://github.com/".insteadOf ssh://git@github.com/
shell: /usr/bin/bash -e {0}
48s
Run npm ci
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN old lockfile Error: An unknown git error occurred
npm WARN old lockfile at makeError (/opt/hostedtoolcache/node/16.20.2/x64/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
npm WARN old lockfile at /opt/hostedtoolcache/node/16.20.2/x64/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
npm WARN old lockfile at runMicrotasks ()
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm WARN old lockfile Could not fetch metadata for midi@git+ssh://git@github.com/paulrosen/MIDI.js.git#e593ffef81a0350f99448e3ab8111957145ff6b2 GitUnknownError: An unknown git error occurred
npm WARN old lockfile at makeError (/opt/hostedtoolcache/node/16.20.2/x64/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
npm WARN old lockfile at /opt/hostedtoolcache/node/16.20.2/x64/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
npm WARN old lockfile at runMicrotasks ()
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:96:5) {
npm WARN old lockfile cmd: 'git',
npm WARN old lockfile args: [
npm WARN old lockfile '--no-replace-objects',
npm WARN old lockfile 'ls-remote',
npm WARN old lockfile 'ssh://git@github.com/paulrosen/MIDI.js.git'
npm WARN old lockfile ],
npm WARN old lockfile code: 128,
npm WARN old lockfile signal: null,
npm WARN old lockfile stdout: '',
npm WARN old lockfile stderr: 'remote: Repository not found.\n' +
npm WARN old lockfile "fatal: repository 'https://github.com/paulrosen/MIDI.js.git/' not found\n"
npm WARN old lockfile }
npm WARN deprecated w3c-hr-time@1.0.1: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated trim@0.0.1: Use String.prototype.trim() instead
npm WARN deprecated stylelint-processor-html@1.0.0: Please use stylelint-processor-arbitrary-tags https://github.com/mapbox/stylelint-processor-arbitrary-tags
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated source-map-resolve@0.5.1: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated rimraf@2.6.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated sane@2.5.2: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated request-promise-native@1.0.5: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm WARN deprecated
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated request@2.88.0: request has been deprecated, see request/request#3142
npm WARN deprecated osenv@0.1.4: This package is no longer supported.
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated mixin-deep@1.3.0: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated kleur@2.0.1: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm WARN deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated har-validator@5.1.0: this library is no longer supported
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated eslint-loader@2.1.0: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated are-we-there-yet@1.1.4: This package is no longer supported.
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated abab@2.0.0: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated vue@2.5.17: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm WARN deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated electron-releases@2.1.0: this package is no longer updated, please fetch version information from https://releases.electronjs.org/releases.json instead
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated core-js@2.5.3: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! remote: Repository not found.
npm ERR! fatal: repository 'https://github.com/paulrosen/MIDI.js.git/' not found

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T23_00_29_229Z-debug-0.log
Error: Process completed with exit code 128.
"

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the dependency chain for MIDI.js
echo "=== Checking package.json for direct MIDI dependencies ==="
cat package.json | grep -i midi || echo "No direct MIDI dependency in package.json"

echo -e "\n=== Checking package-lock.json for MIDI.js references ==="
grep -B5 -A5 "paulrosen/MIDI.js" package-lock.json | head -30

echo -e "\n=== Finding which package depends on MIDI.js ==="
# Search for the parent dependency
grep -B20 "paulrosen/MIDI.js" package-lock.json | grep "\"version\":" | tail -5

echo -e "\n=== Check abcjs dependency (likely parent) ==="
grep -A30 "\"abcjs\":" package-lock.json | head -35

Length of output: 2572

---

🌐 Web query:

abcjs latest version npm MIDI.js dependency

💡 Result:

Short answer: The current npm release line is 6.x (latest published 6.0.0 / 6.0.0-beta series) and abcjs does NOT ship midi.js as a regular dependency. Since the 6.0.0-beta.26/26→28 changes, midi.js was removed as a direct dependency (midi.js was made a peerDependency / optional external for the old MIDI playback code); modern abcjs audio uses its own WebAudio/soundfont approach. [1][2]

Sources:

• abcjs npm notes (6.0.0 / beta releases; midi.js changed to peerDependency / last support note). [1]
• abcjs npm notes (historical 5.x docs showing earlier midi.js packaging). [2]

---

@supervoidcoder Great catch! I found the root cause. The issue is that abcjs version 6.x has removed MIDI.js as a regular dependency, but your package-lock.json is locked to the old abcjs@5.2.0 which depends on the now-deleted MIDI.js repository.

🔍 Root Cause

The error shows: "fatal: repository 'https://github.com/paulrosen/MIDI.js.git/' not found" - the MIDI.js repository no longer exists on GitHub, and your project is locked to abcjs@5.2.0 which requires it.

✅ Solution

We need to update to abcjs@6.x and regenerate the lockfile. Here's the updated workflow:

📝 Key Changes

1. Removed the git config workaround (no longer needed)
2. Added rm -f package-lock.json to delete the old lockfile
3. Changed from npm ci to npm install - this will:
   • Upgrade abcjs from 5.2.0 to 6.x (compatible with ^5.2.0 in package.json)
   • Generate a new package-lock.json without the broken MIDI.js dependency
   • Resolve all other dependencies

🚀 Next Steps

Commit and push this updated workflow file. The build should succeed this time because abcjs 6.x doesn't depend on the missing MIDI.js repository!

---

🏁 Script executed:

#!/bin/bash
# Update the workflow to use npm install and regenerate lockfile
cat > .github/workflows/deploy-pages.yml << 'EOF'
name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'
          cache: 'npm'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Install dependencies
        run: npm install

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4
EOF

echo "✅ Updated workflow file created!"
cat .github/workflows/deploy-pages.yml

Length of output: 1420

---

@supervoidcoder Perfect! ✅ I've updated the workflow file with the fix.

📋 Summary of Changes

The Problem: Your package-lock.json locked abcjs to version 5.2.0, which depends on a now-deleted GitHub repository (paulrosen/MIDI.js).

The Solution: The updated workflow:

1. Deletes the old package-lock.json
2. Uses npm install (instead of npm ci) to regenerate the lockfile
3. This automatically upgrades abcjs from 5.2.0 → 6.x, which doesn't require MIDI.js

🚀 Next Steps

1. Commit and push the updated .github/workflows/deploy-pages.yml file
2. The workflow will automatically run and should succeed this time!
3. Your site will be deployed to: https://omniblocks.github.io/NotebookWriter/

Would you like me to update issue #1 with a summary of the solution?

[supervoidcoder]

@coderabbitai omg this ancient codebase sucks
Run npm install
npm install
shell: /usr/bin/bash -e {0}
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: stackedit@5.15.4
npm ERR! Found: webpack@2.7.0
npm ERR! node_modules/webpack
npm ERR! dev webpack@"^2.6.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^3.0.0 || ^4.0.0" from sass-loader@7.3.1
npm ERR! node_modules/sass-loader
npm ERR! dev sass-loader@"^7.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/runner/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T23_08_45_024Z-debug-0.log
Error: Process completed with exit code 1.

---

Btw u can't modify the codebase can u páste it here

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder I totally understand the frustration! 😅 Old codebases with legacy dependencies can be a pain. You're right, I can't modify the codebase directly - I can only provide you with the workflow file to copy and paste.

🔧 The Fix

The issue is that modern npm is strict about peer dependencies. The old webpack 2.7.0 doesn't satisfy sass-loader's requirement. We'll use --legacy-peer-deps to bypass this check (which is fine for legacy projects like this).

📄 Here's the complete updated workflow file:

Copy this entire content and paste it into .github/workflows/deploy-pages.yml:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'
          cache: 'npm'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Install dependencies
        run: npm install --legacy-peer-deps

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

🔑 Key Change

Changed npm install to npm install --legacy-peer-deps - this tells npm to ignore peer dependency conflicts, which is necessary for this legacy codebase.

Just copy-paste this into your workflow file, commit, and push. This should finally work! 🤞

[supervoidcoder]

@coderabbitai it's still trying to get midi.js check the file

npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/paulrosen/MIDI.js.git
npm ERR! remote: Repository not found.
npm ERR! fatal: repository 'https://github.com/paulrosen/MIDI.js.git/' not found
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T23_14_11_501Z-debug-0.log
Error: Process completed with exit code 128.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the current package.json abcjs version
echo "=== Checking package.json for abcjs version ==="
cat package.json | grep -A2 -B2 "abcjs"

echo -e "\n=== Check if package.json has resolutions or overrides ==="
cat package.json | grep -A5 "resolutions\|overrides" || echo "No resolutions or overrides found"

echo -e "\n=== Full package.json dependencies section ==="
cat package.json | jq '.dependencies, .devDependencies' 2>/dev/null || cat package.json

Length of output: 3513

---

@supervoidcoder Ah, I see the issue now! 🎯 The problem is that package.json has "abcjs": "^5.2.0", which locks it to version 5.x that still needs MIDI.js. The ^ caret only allows updates within 5.x (like 5.2.1, 5.3.0), but won't jump to 6.x.

Since you mentioned I can't modify the codebase, here are two solutions - pick whichever you prefer:

🔧 Option 1: Update package.json manually (Recommended)

Change this line in your package.json:

"abcjs": "^5.2.0",

To:

"abcjs": "^6.0.0",

Then use this workflow:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Install dependencies
        run: npm install --legacy-peer-deps

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

🚀 Option 2: Force upgrade in workflow (No codebase changes)

If you don't want to touch package.json, use this workflow that explicitly upgrades abcjs:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Upgrade abcjs to v6
        run: npm install abcjs@^6.0.0 --legacy-peer-deps

      - name: Install remaining dependencies
        run: npm install --legacy-peer-deps

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

Option 2 is cleaner since it doesn't require you to modify the codebase - just update the workflow file! The key addition is the "Upgrade abcjs to v6" step that forces the upgrade before the main install.

[supervoidcoder]

@coderabbitai

Navigation Menu
OmniBlocks
NotebookWriter

Code
Issues
1
Pull requests
Actions
Projects
Models
Security
Insights
Deploy to GitHub Pages
Upgrade abcjs dependency to version 6.0.0 benweet#6
Jobs
Run details
Annotations
1 error
build
failed 1 minute ago in 2m 11s
Search logs
3s
1s
4s
0s
0s
1m 59s
Run npm install --legacy-peer-deps
npm WARN deprecated @types/minimatch@6.0.0: This is a stub types definition. minimatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm WARN deprecated
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated trim@0.0.1: Use String.prototype.trim() instead
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm WARN deprecated osenv@0.1.5: This package is no longer supported.
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated phin@3.7.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated sane@2.5.2: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated stylelint-processor-html@1.0.0: Please use stylelint-processor-arbitrary-tags https://github.com/mapbox/stylelint-processor-arbitrary-tags
npm WARN deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated eslint-loader@2.2.1: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
npm WARN deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c -- node scripts/build.js
npm ERR! Building: /opt/hostedtoolcache/node/16.20.2/x64/bin/node /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli '/opt/hostedtoolcache/node/16.20.2/x64/bin/node',
npm ERR! gyp verb cli '/home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using node-gyp@3.8.0
npm ERR! gyp info using node@16.20.2 | linux | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb which failed Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:13:12)
npm ERR! gyp verb which failed at F (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:68:19)
npm ERR! gyp verb which failed at E (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:80:29)
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:89:16
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/index.js:42:5
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21)
npm ERR! gyp verb which failed python2 Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:13:12)
npm ERR! gyp verb which failed at F (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:68:19)
npm ERR! gyp verb which failed at E (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:80:29)
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:89:16
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/index.js:42:5
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21) {
npm ERR! gyp verb which failed code: 'ENOENT'
npm ERR! gyp verb which failed }
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb which succeeded python /usr/bin/python
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Command failed: /usr/bin/python -c import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack File "", line 1
npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! gyp ERR! stack SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
npm ERR! gyp ERR! stack
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:402:12)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1100:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
npm ERR! gyp ERR! System Linux 6.11.0-1018-azure
npm ERR! gyp ERR! command "/opt/hostedtoolcache/node/16.20.2/x64/bin/node" "/home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-sass
npm ERR! gyp ERR! node -v v16.20.2
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T23_19_50_574Z-debug-0.log
Error: Process completed with exit code 1.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check package.json for sass-loader and node-sass configuration
echo "=== Check for node-sass in package.json ==="
cat package.json | grep -A2 -B2 "node-sass\|sass-loader"

echo -e "\n=== Check if there are any sass-loader options in webpack configs ==="
grep -r "sass-loader" build/ config/ 2>/dev/null || echo "No sass-loader config found"

echo -e "\n=== Full devDependencies section ==="
cat package.json | jq '.devDependencies' 2>/dev/null

Length of output: 2655

---

@supervoidcoder I feel your pain! 😅 We're getting closer though - we fixed the MIDI.js issue, now it's just the ancient node-sass that needs Python 2.

The good news: sass-loader (which you already have) works with the modern sass package (dart-sass) that doesn't need Python or native compilation!

📄 Here's the final workflow that should work:

Copy this entire content into .github/workflows/deploy-pages.yml:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Upgrade abcjs to v6 (fixes MIDI.js issue)
        run: npm install abcjs@^6.0.0 --legacy-peer-deps

      - name: Install dependencies (except node-sass)
        run: npm install --legacy-peer-deps

      - name: Replace node-sass with sass (dart-sass)
        run: |
          npm uninstall node-sass
          npm install sass --save-dev --legacy-peer-deps

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

🔑 What this does:

1. Upgrades abcjs to v6 (fixes the MIDI.js issue)
2. Installs all dependencies with legacy peer deps
3. Replaces node-sass with sass - the modern pure-JS alternative that doesn't need Python
4. sass-loader automatically detects and uses sass instead of node-sass

This should finally work! 🤞 The sass package is a drop-in replacement for node-sass and your sass-loader will automatically use it.

[supervoidcoder]

@coderabbitai wait you forgot to add the https instead of ssh back! CSN you repasted it here

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder You're absolutely right! 😅 My bad - I removed that step. Here's the complete corrected workflow with the SSH-to-HTTPS fix included:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main
      - master
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '16'

      - name: Delete old package-lock.json
        run: rm -f package-lock.json

      - name: Configure git to use HTTPS instead of SSH
        run: git config --global url."https://github.com/".insteadOf ssh://git@github.com/

      - name: Upgrade abcjs to v6 (fixes MIDI.js issue)
        run: npm install abcjs@^6.0.0 --legacy-peer-deps

      - name: Install dependencies
        run: npm install --legacy-peer-deps

      - name: Replace node-sass with sass (dart-sass)
        run: |
          npm uninstall node-sass
          npm install sass --save-dev --legacy-peer-deps

      - name: Build
        run: npm run build

      - name: Setup Pages
        uses: actions/configure-pages@v4

      - name: Upload artifact
        uses: actions/upload-pages-artifact@v3
        with:
          path: ./dist

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v4

This workflow now:

1. ✅ Deletes the old lockfile
2. ✅ Configures git to use HTTPS instead of SSH
3. ✅ Upgrades abcjs to v6
4. ✅ Installs dependencies with legacy peer deps
5. ✅ Replaces node-sass with modern sass (dart-sass)
6. ✅ Builds and deploys to GitHub Pages

Copy-paste this into .github/workflows/deploy-pages.yml and it should work! 🚀

[supervoidcoder]

@coderabbitai 1 minute ago in 1m 57s
Search logs
2s
1s
3s
0s
0s
1m 50s
Run npm install abcjs@^6.0.0 --legacy-peer-deps
npm WARN deprecated @types/minimatch@6.0.0: This is a stub types definition. minimatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated acorn-dynamic-import@2.0.2: This is probably built in to whatever tool you're using. If you still need it... idk
npm WARN deprecated consolidate@0.15.1: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm WARN deprecated
npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated trim@0.0.1: Use String.prototype.trim() instead
npm WARN deprecated phantomjs-prebuilt@2.1.16: this package is now deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm WARN deprecated osenv@0.1.5: This package is no longer supported.
npm WARN deprecated npmlog@4.1.2: This package is no longer supported.
npm WARN deprecated gauge@2.7.4: This package is no longer supported.
npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm WARN deprecated fstream@1.0.12: This package is no longer supported.
npm WARN deprecated @braintree/sanitize-url@3.1.0: Potential XSS vulnerability patched in v6.0.0.
npm WARN deprecated phin@3.7.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated domexception@1.0.1: Use your platform's native DOMException instead
npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated sane@2.5.2: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm WARN deprecated move-concurrently@1.0.1: This package is no longer supported.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated stylelint-processor-html@1.0.0: Please use stylelint-processor-arbitrary-tags https://github.com/mapbox/stylelint-processor-arbitrary-tags
npm WARN deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated favicons-webpack-plugin@0.0.9: out of support - please update
npm WARN deprecated eslint-loader@2.2.1: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
npm WARN deprecated babel-eslint@8.2.6: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
npm WARN deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated node-sass@4.14.1: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm WARN deprecated vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c -- node scripts/build.js
npm ERR! Building: /opt/hostedtoolcache/node/16.20.2/x64/bin/node /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli '/opt/hostedtoolcache/node/16.20.2/x64/bin/node',
npm ERR! gyp verb cli '/home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using node-gyp@3.8.0
npm ERR! gyp info using node@16.20.2 | linux | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb which failed Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:13:12)
npm ERR! gyp verb which failed at F (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:68:19)
npm ERR! gyp verb which failed at E (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:80:29)
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:89:16
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/index.js:42:5
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21)
npm ERR! gyp verb which failed python2 Error: not found: python2
npm ERR! gyp verb which failed at getNotFoundError (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:13:12)
npm ERR! gyp verb which failed at F (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:68:19)
npm ERR! gyp verb which failed at E (/home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:80:29)
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/which/which.js:89:16
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/index.js:42:5
npm ERR! gyp verb which failed at /home/runner/work/NotebookWriter/NotebookWriter/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21) {
npm ERR! gyp verb which failed code: 'ENOENT'
npm ERR! gyp verb which failed }
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb which succeeded python /usr/bin/python
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Command failed: /usr/bin/python -c import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack File "", line 1
npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! gyp ERR! stack SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
npm ERR! gyp ERR! stack
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:402:12)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1100:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
npm ERR! gyp ERR! System Linux 6.11.0-1018-azure
npm ERR! gyp ERR! command "/opt/hostedtoolcache/node/16.20.2/x64/bin/node" "/home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /home/runner/work/NotebookWriter/NotebookWriter/node_modules/node-sass
npm ERR! gyp ERR! node -v v16.20.2
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2025-11-25T23_27_00_301Z-debug-0.log
Error: Process completed with exit code 1.