fix(warning): Supress warnings when importing experimental web stream from NodeJS

[jimmywarting]

The purpose of this PR is:

... To suppress the warning message when ppl include fetch-blob in their projects

This is what had to change:

... i override process.emitWarning with a noop-fn. Import web/stream and then reassign the warning fn back to what it was

This is what I like reviewers to know:

The test are also importing web/stream's so a warning is still emitted while developing. just running node index.js don't emit any warning

---

• I prefixed the PR-title with docs: , fix(area): , feat(area): or breaking(area):
• I updated ./CHANGELOG.md with a link to this PR or Issue

---

• fix require "stream/web" produces warning #114

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@836709f). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main      #125   +/-   ##
========================================
  Coverage        ?   100.00%           
========================================
  Files           ?         4           
  Lines           ?       448           
  Branches        ?        73           
========================================
  Hits            ?       448           
  Misses          ?         0           
  Partials        ?         0           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 836709f...7e4a063. Read the comment docs.

[benmccann]

I don't know if I'd necessarily prefix everything with node: as it introduces a small performance overhead. It is useful for the import of stream/web which is not available on all versions of Node though so that it can be more easily detected as a Node import by static analysis tools run by Netlify so that their deployments succeed

[LinusU]

as it introduces a small performance overhead.

Hmm, do you have a source on this? I think that it's the new recommended way since the Node.js documentation is switching over to the node:-style.

[benmccann]

I was basing that statement off the fact that the docs say it skips the require cache: https://nodejs.org/api/modules.html#modules_core_modules

I don't know what if any performance impact that has, but I had assumed there would be some small impact

[jimmywarting]

I like the node: prefix...

[andersk]

@benmccann Bypassing the require cache makes it faster, not slower, since core modules are not added to the require cache either way.

[zdm]

Best way:

• load web/streams on demand only, when user requires blob with the steams support;
• keep warning, so user can know, that he use unstable api;