We should seek to move away from referencing Node.js built-ins from modules, e.g. import { parse } from 'url';, where 'url' is a reference to a browser-compatible variant of the Node url module.

Reasons include:

• These automated polyfills are slated for removal in future versions of Webpack (reference)
• There is redundancy with other module usage such as the use of qs in the @wordpress/url package
  • Contributes to larger overall bundle sizes
• The polyfills are not implemented using ES Modules and thus require pulling in much more code than is actually used (example, see full list)

Instances:

• gutenberg/packages/block-library/src/embed/embed-preview.js

  Line 10 in 837fda7

  import { parse } from 'url';

• gutenberg/packages/editor/src/editor-styles/transforms/url-rewrite.js

  Line 4 in 837fda7

  import { parse, resolve } from 'url';

(Questionable: Instances within @wordpress/e2e-tests and @wordpress/e2e-test-utils ? These may be compiled with Webpack, despite not being intended for use in a browser)

With this, it should be considered to disable automatic polyfills from Webpack (reference).