Szymon Łągiewka 41113599af fix(refactor): prefix built-in node module imports ... Since v5 relies on node >= 18, this is now possible (since v16, v14.18.0 [^1][^2]). It's functionally irrelevant: 1. It's not required for CJS nor ESM (with a few exceptions [^3]) 2. It has no performance promises However, there are upsides to this approach: 1. It brings clear boundaries to what's a built-in and what's an external dependency 2. It reduces the risk of importing unwanted deps where a built-in is expected 3. It's slightly more interoperable with other JS runtimes that provide node compatibility[^4], albeit only during development. Once imported from npm, built-ins are assumed. [^1]:https://nodejs.org/docs/latest-v22.x/api/modules.html#built-in-modules [^2]:https://github.com/nodejs/node/pull/37246 [^3]:https://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix [^4]:https://docs.deno.com/runtime/fundamentals/node/#using-node's-built-in-modules		2025-01-10 11:53:44 -06:00
..
public	fix route-separation example	2012-10-09 19:31:52 -07:00
views	examples: fixup html	2022-03-20 15:14:33 -04:00
index.js	fix(refactor): prefix built-in node module imports	2025-01-10 11:53:44 -06:00
post.js	examples: use strict mode	2022-02-02 01:30:51 -05:00
site.js	examples: use strict mode	2022-02-02 01:30:51 -05:00
user.js	Delete back as a magic string (#5933)	2024-09-09 20:28:55 -07:00