Why can't I use TSX? Please help me translate this.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
{
"apps": [
{
"name": "server",
"script": "src/server/main.ts",
"interpreter": "node",
"interpreterArgs": "--import tsx",
"watch": true
}
]
}
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
0|server | node: bad option: --import
Contributor guide
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.
Research direction
Start with the PM2 app configuration shown in the issue, especially the interpreter and interpreterArgs entries, and reproduce the failure while running src/server/main.ts. Trace how PM2 passes these arguments to Node; done means the supported TSX startup path is identified and the bad-option failure is resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, typescript
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100