build:apidoc fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- build-system
Research direction
Start by inspecting the package scripts behind pnpm run build:apidoc and the related build:themedoc command, then read scripts/build-apidoc.ts and scripts/build-themedoc.ts. Verify the commands' TypeScript execution setup and run pnpm run build:apidoc; done means the command completes without failing.
Written by the indexing model from the issue text.
Description
Describe the bug
pnpm run build:apidoc fails, because npm run build:apidoc && npm run build:themedoc are trying to execute the scripts/build-apidoc.ts and scripts/build-themedoc.ts directly via node.
The typescript files could be executed with ts-node or tsx. From node@23 upwards there is an experimental flag to execute ts directly but for the moment I would stick with tsx.
I would recomend tsxover ts-node for simplicity and perrformance reasons.
Pull Request Link
No response
Reason for not contributing a PR
- Lack of time
- Unsure how to implement the fix/feature
- Difficulty understanding the codebase
- Other
Other Reason
No response
Reproducer
Environment
Ubuntu 24
node 22
Angular version
19
PrimeNG version
v19
Node version
22
Browser(s)
No response
Steps to reproduce the behavior
Runningpnpm run build:apidoc fails.
Expected behavior
pnpm run build:apidoc should not fail.
- Dominant language
- TypeScript
- Stars
- 12.5k
- Forks
- 5.1k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from primefaces/primeng
-
Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
primefaces/primeng#19634 ·
-
Component: Documentation Type: Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
primefaces/primeng#19618 ·
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
primefaces/primeng#19531 ·
-
Component: Accessibility Status: Needs Triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
primefaces/primeng#19527 ·
-
good first issue Status: Needs Triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
primefaces/primeng#19516 ·
All issues in primefaces/primeng
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·