mirror of
https://github.com/denoland/deno.git
synced 2025-01-21 13:00:36 -05:00
2091691164
See the comment https://github.com/denoland/deno/pull/25470#issuecomment-2435077722 for the reason why we do this workaround to make `make-fetch-happen` work in Deno This PR applies the same workaround to `npm-check-updates` package. `npm-check-updates` internally uses [`npm-registry-fetch`](https://www.npmjs.com/package/npm-registry-fetch) which uses [`make-fetch-happen`](https://www.npmjs.com/package/make-fetch-happen) (the problematic package) for making http request to npm registry. The detection of `make-fetch-happen` doesn't work for `npm-check-updates` because we use call stack at `net.Socket` constructor to check if it's called from `make-fetch-happen`, but `npm-check-updates` bundles its dependency and the check doesn't work. This PR adds the check of `npm-check-updates` string in call stack in net.Socket constructor to trigger the workaroud. closes #27629 |
||
---|---|---|
.. | ||
benchmarks | ||
ops | ||
polyfills | ||
build.rs | ||
Cargo.toml | ||
clippy.toml | ||
global.rs | ||
lib.rs | ||
polyfill.rs | ||
README.md |
deno_node
require
and other node related functionality for Deno.