👋 @sindresorhus!
I was fiddling with prettier-vscode and noticed an issue with find-up’s import from node:path. When running yarn test, the extension was crashing by saying that it could not resolve node:path.
According to v6.0.0 CHANGELOG and package.json → engines, find-up is expected to work on any Node version that supports ESM. However, looks like node:path import has a stricter constraint, more specifically Node 14.18 and Node 16+.
👋 @sindresorhus!
I was fiddling with prettier-vscode and noticed an issue with
find-up’s import fromnode:path. When runningyarn test, the extension was crashing by saying that it could not resolvenode:path.According to v6.0.0 CHANGELOG and package.json → engines,
find-upis expected to work on any Node version that supports ESM. However, looks likenode:pathimport has a stricter constraint, more specifically Node 14.18 and Node 16+.