Remove mason-js dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 41
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The mason-js dependency is unmaintained and frozen, but still currently used inside of vtcomposite. It has been unmaintained since 2018. For a while it seemed like mason-js would again see maintenance (enough that security issues related to out-of-date binaries and mason-js JS dependencies could be mitigated). But, in effect, mason-js not been maintained since 2018 and therefore I think it is critical to acknowledge this and take action downstream (here).
So, my recommendation is to remove the dependence on mason-js in vtcomposite.
To do this would involve:
- Removing
mason-jsfrom https://github.com/mapbox/vtcomposite/blob/ffdea5a7749fb784fbcf8122e2a4c89e725bd777/package.json#L20 - Removing the
mason-versions.ini - Implementing an alternative method for fetching up to date and reliable versions of dependencies that are currently being installed by
mason-js
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 with package.json at the referenced dependency entry and mason-versions.ini, then trace how vtcomposite currently uses mason-js to install dependencies. Identify a maintained replacement for fetching reliable dependency versions. Done means mason-js and mason-versions.ini are removed and dependency fetching works through the replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100