ESM Build
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- build-system, web-dev
Research direction
Start by inspecting the repository's current package and build entry points to understand how the existing output is produced. Verify the proposed ESM import in a browser or edge-worker-compatible environment; done means the package ships an ESM build that can resolve references there without breaking existing consumers.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal
Ship an ESM build for json-schema-ref-resolver so this code could run in a browser (or edge worker) environment.
Motivation
ESM is the new standard; packages should ship an ESM build for compatibility.
Example
import { RefResolver } from 'json-schema-ref-resolver'
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 5
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jfromaniello/url-join#134 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
quarto-dev/quarto-cli#15042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
extendr/extendr.github.io#134 ·