TEN-framework / TEN-framework/ten-framework
When the app is a Node.js app, it should also truly support dynamic loading of the required addons/extensions from the graph
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
When the app is not a Node.js app, a Node.js addon loader is used to perform on-demand dynamic loading of addons/extensions. However, currently, when the app is a Node.js app (including standalone tests for Node.js addons), all Node.js addons/extensions are loaded upfront. We need to enhance the Node.js addon loader so that it also supports the case when the app itself is a Node.js app, enabling true on-demand dynamic loading of Node.js addons/extensions.
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
Start by tracing the Node.js addon loader and the graph-based addon loading path, then compare behavior when the app is a Node.js app with behavior for other apps. Done means Node.js apps and standalone Node.js addon tests load only the addons or extensions required by the graph, rather than loading all of them upfront.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100