LivelyKernel / LivelyKernel/lively4-core
Update imports in workspaces when modules change
Open
comp: module system
comp: transpilation
effort2: medium (days)
P4: nice to have
type: feature
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Workspaces should be treated differently than normal modules.
Normal modules: A change of a loaded dependent module will trigger a change of the whole module.
Workspace:
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing how imports and dependent-module changes are handled for normal modules and workspaces; done should mean a changed loaded dependency updates workspace imports without triggering the whole workspace module to change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100