Limiting require to Sub-package exports was a bad idea

[alexp1917]

Version

16.6.0

Platform

Linux HOST 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

the docs themselves agree that this change will break things - https://nodejs.org/api/all.html#packages_package_entry_points

How often does it reproduce? Is there a required condition?

require('your-package/package.json') is a well known way to get the reflective property of what version of a module you have loaded.

What is the expected behavior?

the people who run node prevent bad ideas from being merged into the main release

What do you see instead?

the community failing to admitt that a decision was wrong + rolling it back

Additional information

thanks for reading

[aduh95]

Looks like a duplicate of #33460, see the discussion there for workaround and replacement API design discussion.