NASA-AMMOS / NASA-AMMOS/plandev-ts-user-code-runner
Support imports
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Supporting imports is likely to be a really tricky thing. We need to be able to resolve the imports PRIOR to type checking and retrieve them at that point for compilation (with a caller provided resolver/loader). This likely means pre-parsing the file into an AST to grab import statements and resolve them. I don't think there are any explicit security concerns here, but we should think about it.
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.
Research direction
The issue names no files, tests, or entry points, so first locate the type-checking and compilation flow. Determine how a caller-provided resolver or loader should supply imports before type checking, including the security implications. Done means imported modules are resolved and available during compilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100