frostney / frostney/GocciaScript
Add a bundle-backed resolver and runtime source registry
Open
Nobody has claimed this yet.
new feature
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Goal
Allow runtime module resolution from virtual bundle paths instead of filesystem paths.
Scope
- Implement bundle-backed resolver and source-provider support for
.gcbundlecontents. - Resolve import-map and alias-expanded paths against bundle virtual paths.
- Enforce bundle-root boundaries.
- Load JSON modules from bundled JSON text instead of disk.
Acceptance Criteria
- Bundled resolution only resolves bundled paths.
- There is no filesystem fallback in bundle mode.
- JSON imports succeed from bundled content.
- Errors for missing bundle entries are deterministic and explicit.
Stand-alone Value
Makes bundle execution possible without native executable packaging.
Dependencies
Depends on #152 and #153.
Tracking
Tracked by #161.
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 by reading dependencies #152 and #153 and the tracking issue #161 to understand the existing bundle model and resolver entry points. Verify completion against the acceptance criteria: bundled-only resolution with root-boundary enforcement, bundled JSON imports, no filesystem fallback, and deterministic missing-entry errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100