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

Add global config for "fork scopes"

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
nodejs, typescript
Domain
tooling

Research direction

Start by tracing how global configuration is loaded and how the local .indo.json alias setting is applied. Verify the vendor/@foo/bar and vendor/bar lookup behavior, then confirm that a global fork-scope setting makes @foo/bar an alias only when the scoped path exists and the unscoped path does not.

Written by the indexing model from the issue text.

Description

enhancement

If I use the npm package scope @foo for npm forks, I should be able to tell Indo to treat @foo/bar as a suitable alias for bar (assuming vendor/@foo/bar exists and vendor/bar does not).

Current workaround: Set "alias": { "bar": "@foo/bar" } in the local .indo.json file

Dominant language
TypeScript
Stars
18
Forks
0
PR merge metrics
No merged PRs in 30d

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 alloc/indo

All issues in alloc/indo

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.