Un-experimental DecompressInterceptor
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, node.js
- Domain
- backend
Research direction
Start by reading the decompress interceptor implementation and the code that emits its experimental warning; the issue does not name their file paths. Remove the warning when creating the interceptor, then verify that creation works without the warning and that decompression behavior remains intact.
Written by the indexing model from the issue text.
Description
This would solve...
It would allow jsdom, which uses Undici's lower-level features, to reuse Undici's maintained decompression interceptor, instead of bundling our own.
The implementation should look like...
Remove the experimental warning on creating a decompress interceptor.
I have also considered...
Just copying it into jsdom. That is the current solution.
Additional context
I thought even if you aren't ready to expose it now, a tracking issue might be appreciated.
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 931
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 92
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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.
More from nodejs/undici
-
MockPool/MockClient `cleanMocks()` doesn't clear the interceptors that Node.js global fetch usesPossibly taken @Anoesj claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Fix `test:typescript` script for Windows compatibilityPossibly taken @shivarm claimed this 19 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Socks5ProxyAgent: SOCKS5 handshake/auth timeout leaks the underlying socketPossibly taken @drewmt claimed this 60 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
DispatchOptions.upgrade accepts boolean in types but runtime rejects itPossibly taken @mcollina claimed this 109 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Default fetch timeout too shortMay be free again A pull request for this issue was closed without being merged. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nodejs/undici#1373 · 20 comments · 15 reactions ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/harper#3299 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
osmlab/name-suggestion-index#12992 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-government-design-system/ogds-elements#199 ·
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Document annotations cannot anchor visible code after a shorter or different fenced-code markerOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#16898 ·
Maintainers usually reply within 1 day