Skip to content

docs: add vscode-open-in-npmx to the readme#1448

Merged
danielroe merged 1 commit intonpmx-dev:mainfrom
sybers:patch-2
Feb 12, 2026
Merged

docs: add vscode-open-in-npmx to the readme#1448
danielroe merged 1 commit intonpmx-dev:mainfrom
sybers:patch-2

Conversation

@sybers
Copy link
Copy Markdown
Contributor

@sybers sybers commented Feb 12, 2026

Hey!

I quickly made this extension to have a command to open currently selected text or current package on npmx.dev.

I know there's already a VSCode extension, but I wanted something dead simple just to have a shortcut and I think some other folks might also just need this.

I'd understand if you'd prefer to keep only the official extension in the Readme :)

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Feb 12, 2026 9:11pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Feb 12, 2026 9:11pm
npmx-lunaria Ignored Ignored Feb 12, 2026 9:11pm

Request Review

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 12, 2026

📝 Walkthrough

Walkthrough

The README.md file was updated in the "Related projects" section. The old npmx VSCode extension entry was replaced with an updated "Official" vscode-npmx entry, and a new vscode-open-in-npmx entry was added. The changes modify the displayed project references and external VSCode extension listings without affecting code behaviour or altering any exported or public entities.

Possibly related PRs

Suggested reviewers

  • danielroe
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main
Description check ✅ Passed The pull request description is directly related to the changeset, explaining the motivation for adding a new VSCode extension entry to the README.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

@danielroe danielroe changed the title feat(docs): add vscode-open-in-npmx to the Readme docs: add vscode-open-in-npmx to the readme Feb 12, 2026
@danielroe danielroe added this pull request to the merge queue Feb 12, 2026
Merged via the queue into npmx-dev:main with commit 11c33f2 Feb 12, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants