Improve compatibility with browser by using better APIs

[fregante]

The browser compatibility claimed by this package is only due to bundlers’ polyfills, which are increasingly missing:

• Can't using in Vite2 #257
• No polyfills for node modules http and https with Webpack 5 (via CRA 5) #254
• Remove import of inspect from utils JS-DevTools/ono#17
• Error: Uncaught (in promise): ReferenceError: process is not defined #137
• [Build] Don't work production build with @apidevtools/json-schema-ref-parser, but development mode it's work  #267

• json-schema-ref-parser/lib/util/url.js

  Lines 25 to 26 in 5d7f895

  	exports.parse = require("url").parse;
  	exports.resolve = require("url").resolve;

• json-schema-ref-parser/lib/util/url.js

  Line 3 in ce23669

  let isWindows = /^win/.test(process.platform),

http and https can be replaced by fetch, which is available in Node 18 and can already be used everywhere with https://github.com/matthew-andrews/isomorphic-fetch. I think this would also avoid Buffer issues

URLs can be parsed with the URL constructor, available globally in Node 10.

They can all be replaced by their modern and cross-platform equivalents or they can use something like globalThis.process?.platform to ensure that they don't immediately fail when missing.

[philsturgeon]

Thank you, this makes for a great Epic for folks to work from.

If anyone can take a swing at knocking out a few of these that sounds be hugely helpful.

[cihad]

Maybe this will help: https://stackblitz.com/edit/webpack-webpack-js-org-vcdpkp?file=src/index.js

[alanpoulain]

I've taken it, please wait for the PR when the Hacktoberfest starts 😄

[paztis]

it seems node-fetch dependency recreate this issue.
How to compile it now for browsers in webpack ?

node-fetch is importing node:http instead of http, node"fs instead of fs, ....
So all webapck classiuc NodePolyfills are no more working