zio/zioinfo-mail
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a4a5d352b8
zioinfo-mail/app/node_modules/@remix-run/web-fetch
History
DESKTOP-TKLFCPR\ython 11c670f2a0 refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 
- 37개 파일 IP → zioinfo.co.kr 치환 (소스/매뉴얼/설정/하네스)
- Manager DrConsole/NetworkConsole/CsapConsole 빌드 + /var/www/manager/ 배포
- 테스트: Manager HTTP 200, ITSM 신규 API 7개 전체 200

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-31 10:09:17 +09:00
..
src refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
LICENSE.md refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
package.json refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
Readme.md refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00

Readme.md

@remix-run/web-fetch

ci package downloads

Web API compatible fetch API for nodejs.

Comparison to Alternatives

node-fetch

The reason this fork exists is because node-fetch chooses to compromise Web API compatibility and by using nodejs native Readable stream. They way they put it is:

  • Make conscious trade-off when following [WHATWG fetch spec][whatwg-fetch] and stream spec implementation details, document known differences.
  • Use native Node streams for body, on both request and response.

We found these incompatibility to be really problematic when sharing code across nodejs and browser rutimes. This library uses @remix-run/web-stream instead.