LivelyKernel / LivelyKernel/lively4-core
Relative js import in markdown works differently in container and lively-markdown
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
e.g. in .md file
```
import { something } from './../relative.js';
```
Refers to correct file in view mode in a container, but is resolved relative from `lively4url` in a lively-markdown component outside a container:
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 relative import from the issue's markdown example in both view mode inside a container and in a lively-markdown component outside one. Compare how each context resolves './../relative.js', then verify that both contexts resolve the import to the file relative to the markdown document.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100