LivelyKernel / LivelyKernel/lively.server
Redirect messes up system.js error reporting
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
system.js tries to remove itself from error stack.
In `addToError()` it looks at `$__curScript`, which is
`https://lively-next.org/lively.next-node_modules/systemjs/dist/system.src.js`
(derived from the `src` tag of its own `script` element) but the stack trace has
`https://lively-next.org/lively.next-node_modules/systemjs/0.19.47/dist/system.src.js`
because of the `HTTP/1.1 301 Moved Permanently` server response.
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 in system.js at addToError() and inspect how $__curScript is obtained from the script element. Compare that URL with the redirected URL present in the stack trace, then run the existing error-reporting tests or browser reproduction if available. Done means the system.js entry is removed correctly from error stacks when the script was served through a redirect.
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