LivelyKernel / LivelyKernel/lively.modules
new module creation + import issue
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
- in existing module
foo.jsadd import for non-existent moduleimport Bar from "./bar.js" - create
bar.jswithexport default class Bar {} - return to
foo.js. expected:Baris defined but it isn't right now
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
Reproduce the issue in the existing foo.js by importing the initially missing ./bar.js, then creating bar.js with its default export. Start by tracing the module update or import-resolution entry point; done means Bar becomes defined in foo.js after bar.js is created, without reloading the module manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100