BUG | Graph | simple graph not fully visible when zoomed out
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Open the graph reproduction at https://node-modules.dev/graph#selected=@vue/[email protected]&install=@vueuse/core, toggle the simple graph, and zoom out to the maximum level. Trace the graph view's rendering and viewport behavior; done means the entire simple graph remains visible at maximum zoom out.
Written by the indexing model from the issue text.
Description
Describe the bug
- Open graph
- toggle simple graph
- zoom out (max)
Reproduction
https://node-modules.dev/graph#selected=@vue/[email protected]&install=@vueuse/core
System Info
System:
OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
Memory: 41.87 GB / 62.58 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 23.5.0 - ~/.nvm/current/bin/node
npm: 10.9.2 - ~/.nvm/current/bin/npm
pnpm: 9.15.6 - ~/.nvm/current/bin/pnpm
bun: 1.1.42 - ~/.nvm/current/bin/bun
Browsers:
Chrome: 130.0.6723.69
Used Package Manager
pnpm
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 92
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from antfu/node-modules-inspector
-
Support bun dedupeOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
antfu/node-modules-inspector#214 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
antfu/node-modules-inspector#213 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
antfu/node-modules-inspector#174 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
antfu/node-modules-inspector#145 ·
-
Redundant codeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
antfu/node-modules-inspector#123 · 2 comments ·
All issues in antfu/node-modules-inspector
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
StabilityNexus/Fate-EVM-Frontend#153 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#9039 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Tencent/teamai-cli#862 ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest redis
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
libredb/libredb-studio#1164 ·
Maintainers usually reply within 1 day
-
flake
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day