fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250

Closed
AndresL230 wants to merge 2 commits into
mainfrom
fix/frontend-lockfile-restore-3d
Closed

fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom
fix/frontend-lockfile-restore-3d

Conversation

@AndresL230

@AndresL230AndresL230 commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

What & why

main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.

As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.

What changed

  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.

Testing

  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.

Impact

Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.

🤖 Generated with Claude Code

@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitaiBot commented Jun 22, 2026•
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/frontend-lockfile-restore-3d

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

cloudflare-workers-and-pagesBot commented Jun 22, 2026

Copy link
Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful!
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM

@cloudflare-workers-and-pages

cloudflare-workers-and-pagesBot commented Jun 24, 2026•
edited
Loading

Copy link
Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful!
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM

@Jose-Gael-Cruz-Lopez

Jose-Gael-Cruz-Lopez commented Jul 1, 2026

Copy link
Copy Markdown
Member

Recommend closing this — the issue it fixes is already resolved on main.

Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.

So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).

@AndresL230

AndresL230 commented Jul 8, 2026

Copy link
Copy Markdown
CollaboratorAuthor

Closing as superseded — the bug this fixes is already resolved on main.

The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.

Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
fix(frontend): restore react-force-graph-3d dependency tree in lockfile - #250
Closed
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Closed
fix(frontend): restore react-force-graph-3d dependency tree in lockfile#250
AndresL230 wants to merge 2 commits into
mainfrom 
fix/frontend-lockfile-restore-3d
Conversation
@AndresL230
@AndresL230AndresL230
commented
Jun 22, 2026

Copy link


Copy Markdown

Collaborator
What & why
main's frontend/package-lock.json is missing the react-force-graph-3d dependency subtree (3d-force-graph, three-forcegraph, react-kapsule, kapsule, ngraph.*, …) even though package.json declares react-force-graph-3d@^1.29.1. The tree was dropped during the recent re-arch / dep-bump commits on main.
As a result, npm ci fails with Missing: 3d-force-graph@… from lock file — which reds the Frontend (lint + tsc + vitest) check on main itself and on every open PR (#242, #243, #241), since CI merges each PR with main before installing.
What changed
  • Regenerated frontend/package-lock.json with npm 10.9.2 (the version pinned in ci.yml and used by Cloudflare Workers Builds) via npm install --package-lock-only.
  • Lock-only change — no package.json edits, no source changes.
Testing
  • npm ci with npm 10.9.2 against the regenerated lock → exit 0 (the exact CI command).
  • Restores node_modules/react-force-graph-3d, node_modules/3d-force-graph, node_modules/three-forcegraph entries.
Impact
Merging this unblocks the frontend check on main and lets #242 / #243 / #241 go green on their next CI run.
🤖 Generated with Claude Code
@AndresL230@claude
fix(frontend): restore react-force-graph-3d dependency tree in lockfile
4f5401e
main's package-lock.json was missing the react-force-graph-3d subtree
(3d-force-graph, three-forcegraph, react-kapsule, kapsule, …) even
though package.json declares react-force-graph-3d. `npm ci` therefore
failed ("Missing: 3d-force-graph@… from lock file") on main and on every
open PR's frontend check.
Regenerated package-lock.json with npm 10.9.2 — the CI/Cloudflare-pinned
version — via `npm install --package-lock-only`, then validated with a
full `npm ci` (exit 0). Lock-only change; no package.json or source edits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai
coderabbitaiBot
commented
Jun 22, 2026•

edited

Loading

Copy link


Copy Markdown

Important
Review skipped
Review was skipped due to path filters
⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ca86df76-d61a-4ccf-b7f1-ba2ae2e36434
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
  •  🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  •  Create PR with unit tests
  •  Commit unit tests in branch fix/frontend-lockfile-restore-3d
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment @coderabbitai help to get the list of available commands.
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 22, 2026

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend4f5401eCommit Preview URL

Branch Preview URL		Jun 22 2026, 04:11 AM
@cloudflare-workers-and-pages
cloudflare-workers-and-pagesBot
commented
Jun 24, 2026•

edited

Loading

Copy link


Copy Markdown

Deploying with Cloudflare Workers Cloudflare Workers
The latest updates on your project. Learn more about integrating Git with Workers.
StatusNameLatest CommitPreview URLUpdated (UTC)
✅ Deployment successful! 
View logs		frontend-staging59e5409Commit Preview URL

Branch Preview URL		Jun 24 2026, 04:46 AM
@Jose-Gael-Cruz-Lopez
Jose-Gael-Cruz-Lopez
commented
Jul 1, 2026

Copy link


Copy Markdown

Member
Recommend closing this — the issue it fixes is already resolved on main.
Verified: origin/main's frontend/package-lock.json now contains the full react-force-graph-3d subtree (3d-force-graph, three-forcegraph, etc. — 9 refs), so npm ci no longer fails. Independent confirmation: PR #286's Frontend (lint + tsc + vitest) check is green, and CI runs npm ci against the PR merged with main — which would red if main's lockfile were still broken.
So the lockfile drift this PR restored has since landed on main through another merge, making this redundant. Suggest closing (or, if you'd rather keep it, rebase onto main — it should come out an empty/no-op diff).
@AndresL230
AndresL230
commented
Jul 8, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Closing as superseded — the bug this fixes is already resolved on main.
The missing react-force-graph-3d subtree was restored on main by the lockfile-resync commits (88da564 chore: sync package-lock.json, a1023c4 chore: sync package-lock.json with Node 20), not this PR. On current main all five packages (react-force-graph-3d, 3d-force-graph, three-forcegraph, react-kapsule, ngraph.graph) are present, and the latest CI run (2026-07-08, runId 28924306657) shows Frontend (lint + tsc + vitest) → success with npm ci logging added 1053 packages… in 21s and no Missing: … from lock file error — the exact failure this PR targeted.
Not merging, because this is now a stale +63-line lockfile patch and main's lockfile has been regenerated twice since; re-applying it risks de-syncing the healthy lock and re-breaking npm ci. The 'unblocks #242/#243/#241' rationale is also moot now that main's frontend check is green.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@AndresL230@Jose-Gael-Cruz-Lopez