Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Edge from document to packageInformation

Open
#133 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
devtools

Research direction

Start by reviewing how document, export, and packageInformation edges are currently represented in the LSIF format and implementation. Define the direct document-to-packageInformation relationship, including whether it is an N-to-1 edge, and verify that documents without exports can still resolve their package.

Written by the indexing model from the issue text.

Description

feature-request

I want to split documents based on packages, and I think it is only possible via looking indirectly through one of exports, and if a document doesn't have exports we can't find its package. So an edge between document and packageInformation can be helpful.

By the way, packageInformation edge is a good candidate for N to 1 edges (outVs)?

Dominant language
TypeScript
Stars
198
Forks
40
Avg merge
3d 7h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/lsif-node

All issues in microsoft/lsif-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.