frostney / frostney/GocciaScript
Teach ScriptLoader to execute .gcbundle artifacts in bytecode mode
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
Make .gcbundle the first user-facing bundled artifact by teaching ScriptLoader to execute it.
Scope
- Extend
ScriptLoaderto detect.gcbundleinputs. - Initialize the bundle-backed resolver/runtime in bundle mode.
- Execute the bundle entry module in bytecode mode.
- Preserve current
.jsand.gbcbehavior unchanged.
Acceptance Criteria
./build/ScriptLoader app.gcbundleruns successfully after the original source tree is removed.- Existing
.jsand.gbcworkflows continue to behave the same. - Error reporting in bundle mode includes the bundle virtual path and original source metadata where available.
Stand-alone Value
Delivers deployable bundled apps without any executable wrapping.
Dependencies
Depends on #154, #155, and #156.
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 at the ./build/ScriptLoader entry point and compare its existing .js and .gbc workflows, after reviewing dependencies #154, #155, and #156. Done means app.gcbundle runs after the source tree is removed, existing workflows remain unchanged, and bundle errors include the virtual path and available source metadata.
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