mattrobenolt / mattrobenolt/sourcemap-validator
Doesn't use the relative URL even though browsers do.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 50
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
{
"version": 3,
"file": "_assets/js/bundle.js",
"mappings": "CAAA,WACA,QAAA,IAAA,SACA,QAAA,IAAA",
"sources": [
"./require.js",
"./bundle.js"
],
"names":[]
}
At the URL: https://example.com/assets/source-maps/bundle.js.map. Most browsers will assume "require.js" is at https://example.com/assets/source-maps/require.js, however your validator assumes it's in the same location as the asset itself at https://example.com/assets
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 by tracing how the validator resolves source paths for the provided sourcemap URL, then compare that behavior with browser-relative URL resolution. Done means the example resolves require.js under https://example.com/assets/source-maps rather than https://example.com/assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100