generator-only package
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.7k
- Forks
- 370
- PR merge metrics
- No merged PRs in 30d
Description
I just made a relatively-aggressive fork here that removes the consumer code as well as the reliance on what-wg-url. I have kept all of the license, contributors, etc. in place. All of my changes are deletions and minor fixups to make the tests work.
The goal is to have something small to bundle with peggy's upcoming support for source-map generation.
I apologize for not discussing it here first. I would be happy to either keep the new repo in sync with whatever changes are made here, or defork and hand over the keys to npm if this project is interested in publishing something that uses the name.
Please let me know if it concerns you or you'd like me to take some other action.
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
Review the proposed fork at hildjj/source-map-generator and this issue's discussion first. The issue does not name files or tests; determine whether the project wants to adopt, synchronize with, or reject the generator-only package. Done means the maintainers have chosen a direction and documented the package ownership and publishing plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100