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

Using `indo link` in repo root directory should expose all non-private packages

Open
#53 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
node.js, typescript
Domain
cli, tooling

Research direction

Start at the indo link command entry point and trace how it discovers packages when run from the repository root. Check how private packages are identified, then run the command in a representative workspace; done means all non-private packages are linked to the global registry while private packages are excluded.

Written by the indexing model from the issue text.

Description

enhancement

It can be useful to link all packages in the repo into my global registry at once.

Dominant language
TypeScript
Stars
18
Forks
0
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.