path: add path/posix and path/win32 alias modules

[ExE-Boss]

Turns out, #34055 is not the last alias module, because I forgot about path.posix and path.win32.

---

Refs: #31553
Refs: #32953
Refs: #33950
Refs: #34001
Refs: #34002
Refs: #34055

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[MylesBorins]

RSLGTM

[ExE-Boss]

review?(@jasnell, @mcollina, @targos, @tniessen, @Trott)

[mcollina]

lgtm

[ExE-Boss]

@jasnell @MylesBorins @Trott @targos @BridgeAR

It’s only a few days left until v15.0.0 ships, and I’d like to get this merged before then.

[Trott]

Repeating the comment from #34055 here as well:

We're a few weeks past the semver-major cut-off date for 15.x.x so this would probably require assent from both @nodejs/tsc and Releasers (and in particular @BethGriggs who is preparing the release) to land in 15.x.x.

@richardlau Is this semver major because it might have a naming clash with existing modules? Or is there another reason?

[richardlau]

Repeating the comment from #34055 here as well:

We're a few weeks past the semver-major cut-off date for 15.x.x so this would probably require assent from both @nodejs/tsc and Releasers (and in particular @BethGriggs who is preparing the release) to land in 15.x.x.

@richardlau Is this semver major because it might have a naming clash with existing modules? Or is there another reason?

I was under the impression that new modules were major due to naming clashes (and remember that "existing modules" include things that are not on npm's registry, e.g. local files). I think I did see someone post in an issue that that isn't what is writing down so 🤷.

[BethGriggs]

We're a few weeks past the semver-major cut-off date for 15.x.x so this would probably require assent from both @nodejs/tsc and Releasers (and in particular @BethGriggs who is preparing the release) to land in 15.x.x.

It would probably need to land in the next few hours to make it into v15.0.0 as I don't think we should make changes < 24 hours until the release (unless critical).

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/33718/

[Trott]

CITGM: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2525/

[Trott]

I'm going to be offline for most of the day, but if someone else can try to shepherd this through, that would be great. CITGM spot check looks good to me, so it's really just a matter of resolving whatever lint issues might remain, getting a green CI, and landing.

[codecov-io]

Codecov Report

Merging #34962 into master will decrease coverage by 0.47%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #34962      +/-   ##
==========================================
- Coverage   96.87%   96.40%   -0.48%     
==========================================
  Files         212      222      +10     
  Lines       69609    73681    +4072     
==========================================
+ Hits        67435    71033    +3598     
- Misses       2174     2648     +474     

Impacted Files	Coverage Δ
lib/_http_client.js	98.45% <100.00%> (+0.01%)	⬆️
lib/assert.js	98.09% <100.00%> (+<0.01%)	⬆️
lib/events.js	99.27% <100.00%> (+<0.01%)	⬆️
lib/fs.js	94.13% <100.00%> (-0.14%)	⬇️
lib/internal/assert/assertion_error.js	100.00% <100.00%> (ø)
lib/internal/bootstrap/loaders.js	97.18% <100.00%> (+0.01%)	⬆️
lib/internal/buffer.js	100.00% <100.00%> (ø)
lib/internal/errors.js	97.97% <100.00%> (+<0.01%)	⬆️
lib/internal/event_target.js	97.04% <100.00%> (+<0.01%)	⬆️
lib/internal/fs/read_file_context.js	98.31% <100.00%> (ø)
... and 80 more

---

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 8beef5e...c980bd8. Read the comment docs.

[ljharb]

v15 has already been cut before landing this, which means master is now v16?