Remove mason-js dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 45
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The mason-js dependency is unmaintained and frozen, but still currently used inside of vtquery. 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 vtquery.
To do this would involve:
- Removing
mason-jsfrom thepackage.json - 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 by inspecting package.json, mason-versions.ini, and the places where mason-js is used inside vtquery. Determine how the dependencies listed in mason-versions.ini are currently fetched, then define a reliable replacement approach. Done means mason-js and mason-versions.ini are removed and dependency fetching continues through the alternative method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100