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

Provide best-effort links to contents in `node_modules`

Open
#171 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

The issue names no implementation files or tests. Start by locating the code that formats compiler-error file links, then determine how dependency versions and repository locations can be resolved; done means node_modules locations receive best-effort links to the matching unpkg or GitHub contents.

Written by the indexing model from the issue text.

Description

In cases where an error is reported from a file in node_modules, we end up with output like the following:

packages/utils/devEnv/tsconfig.json
  • error TS2694: Namespace '"/mnt/ts_downloads/_/m/theatre/node_modules/@types/estree/index"' has no exported member 'StaticBlock'.
    • file:///mnt/ts_downloads/_/m/theatre/node_modules/@types/eslint/index.d.ts#L617
    • file:///mnt/ts_downloads/_/m/theatre/node_modules/@types/eslint/index.d.ts#L618
  • error TS2300: Duplicate identifier 'ElementType'.
    • file:///mnt/ts_downloads/_/m/theatre/node_modules/@types/hoist-non-react-statics/node_modules/@types/react/index.d.ts#L3244
    • file:///mnt/ts_downloads/_/m/theatre/node_modules/@types/react/index.d.ts#L3244
  • error TS2300: Duplicate identifier 'LibraryManagedAttributes'.
    • file:///mnt/ts_downloads/_/m/theatre/node_modules/@types/hoist-non-react-statics/node_modules/@types/react/index.d.ts#L3254

I think it would be helpful if we could provide a link to the exact version on unpkg, or more ideally, GitHub if we could really figure that out.

Dominant language
TypeScript
Stars
29
Forks
14
Avg merge
2h 23m
Merged PRs (30d)
7

Getting set up

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/typescript-error-deltas

All issues in microsoft/typescript-error-deltas

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.