ipfs / ipfs/aegir

Docs: Fix retrieval of entry points from consumer's `tsconfig.json`

Open
#1,112 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
105
Forks
62
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Following up from the conversation [here](https://github.com/ipfs/aegir/pull/1107#issuecomment-1328033031) we should be able to parse the `entryPoints` from a user's `tsconfig.json`

**To Reproduce**
Steps to reproduce the behavior:
1. run ```aegir docs```

**Expected behavior**
If a user has a `tsconfig-docs.aegir.json` we should derive the entryPoints from there.

Contributor guide

No contributing guide indexed for this repository

Research direction

Run `aegir docs` with a consumer project that has `tsconfig-docs.aegir.json`, then trace how the command discovers entry points from that configuration. Done means the command derives the entryPoints from the consumer's `tsconfig-docs.aegir.json` instead of failing to retrieve them.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
documentation, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.