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

Support imports

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
compilers

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.

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.

Dominant language
TypeScript
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 NASA-AMMOS/plandev-ts-user-code-runner

All issues in NASA-AMMOS/plandev-ts-user-code-runner

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.