LivelyKernel / LivelyKernel/lively.next
"Import Assistant" in `lively.modules`
Open
Nobody has claimed this yet.
✨ enhancement
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
On a more general note, the lively.modules right now fails silently when certain exports of a module do not exist. I think we can do better than that, by:
- Do log a warning if there are imports that could not be satisfied.
- Give some hints about wether or not the import approach is doomed to begin with, i.e. some packages simply expose all of their entities via a default export.
Originally posted by @merryman in https://github.com/LivelyKernel/lively.next/issues/592#issuecomment-1367231587
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 locating the import handling in lively.modules and trace how exports that cannot satisfy imports are currently handled. The work is done when unsatisfied imports produce warnings and the messages provide hints about packages that expose entities only through a default export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100