module,win: fix long path resolve by huseyinacacak-janea · Pull Request #53294 · nodejs/node

huseyinacacak-janea · 2024-06-03T10:25:51Z

Several issues were encountered with module loading due to extended path lengths on Windows. These have been addressed with corrections implemented across four distinct code locations, accompanied by the addition of a corresponding test case for each to ensure functionality.
Additionally, I've moved es-module/test-GH-50753.js to es-module/test-esm-long-path-win.js as the tests cover more cases than specified in that issue.

Fixes: #50753

targos · 2024-06-03T12:11:39Z

@nodejs/platform-windows

I actually need more time to take a look, I think the implementation will solve the problem but I want to test in which cases we should include the UNC path, since we didn't do this in all paths in the toNamespacedPath.

H4ad · 2024-06-03T13:02:56Z

There are some conditions to include the UNC that you are not following:

node/lib/path.js

Lines 632 to 645 in 58711c2

if(StringPrototypeCharCodeAt(resolvedPath,0)===CHAR_BACKWARD_SLASH){
// Possible UNC root
if(StringPrototypeCharCodeAt(resolvedPath,1)===CHAR_BACKWARD_SLASH){
constcode=StringPrototypeCharCodeAt(resolvedPath,2);
if(code!==CHAR_QUESTION_MARK&&code!==CHAR_DOT){
// Matched non-long UNC root, convert the path to a long UNC path
return`\\\\?\\UNC\\${StringPrototypeSlice(resolvedPath,2)}`;
}
}
}elseif(
isWindowsDeviceRoot(StringPrototypeCharCodeAt(resolvedPath,0))&&
StringPrototypeCharCodeAt(resolvedPath,1)===CHAR_COLON&&
StringPrototypeCharCodeAt(resolvedPath,2)===CHAR_BACKWARD_SLASH
){

Although the condition could be matched, I think it would be better to wait for the migration of toNamespacedPath to C++.

Maybe we could include the ToNamespacePath port in this PR, and then leave that other PR just to remove the JS version and rewrite the places they are used.

@anonrig What do you think?

nodejs-github-bot · 2024-06-03T14:59:37Z

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

anonrig

I prefer to land this after the toNamespacedPath migration to C++. Unfortunately, I don't have the time to pursue this at the moment (afaict, there is only one failing test). I appreciate if you could took over that PR and apply these changes in a follow up PR.

MoLow · 2024-06-03T21:08:30Z

I prefer to land this after the toNamespacedPath migration to C++. Unfortunately, I don't have the time to pursue this at the moment (afaict, there is only one failing test). I appreciate if you could took over that PR and apply these changes in a follow up PR.

in that case, can you convert the blocking "request changes" into a simple suggestion/friendly ask? I don't think this PR should be blocked on a PR that is not being currently worked on

nodejs-github-bot · 2024-06-04T06:11:34Z

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

huseyinacacak-janea · 2024-06-05T06:34:00Z

I prefer to land this after the toNamespacedPath migration to C++. Unfortunately, I don't have the time to pursue this at the moment (afaict, there is only one failing test). I appreciate if you could took over that PR and apply these changes in a follow up PR.

Sure, no problem, I'll take over your PR and start working on it.

nodejs-github-bot · 2024-07-04T01:27:02Z

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

huseyinacacak-janea · 2024-07-05T12:48:14Z

I prefer to land this after the toNamespacedPath migration to C++. Unfortunately, I don't have the time to pursue this at the moment (afaict, there is only one failing test). I appreciate if you could took over that PR and apply these changes in a follow up PR.

@anonrig I've rebased this PR to use toNamespacedPath. Could you please review it?

huseyinacacak-janea · 2024-07-15T11:59:07Z

Is there anything else I can do to help this PR move forward?

anonrig · 2024-07-02T12:45:38Z

- switch (FilePathIsFile(env, file_path)) {
+ Local<Value> local_file_path =
+ Buffer::Copy(
+ env->isolate(), file_path.c_str(), strlen(file_path.c_str()))


Suggested change
env->isolate(), file_path.c_str(), strlen(file_path.c_str()))
env->isolate(), file_path.c_str(), file_path.size())

Fixed. Thanks.

anonrig · 2024-07-15T12:01:21Z

- switch (FilePathIsFile(env, file_path)) {
+ Local<Value> local_file_path =
+ Buffer::Copy(
+ env->isolate(), file_path.c_str(), strlen(file_path.c_str()))


anonrig · 2024-07-15T12:02:06Z

+ // Check if the path has a trailing slash. If so, add it after
+ // ToNamespacedPath() as it will be deleted by ToNamespacedPath()
+ bool slashCheck = !path_value.ToString().empty() &&
+ path_value.ToString().back() ==


Suggested change
path_value.ToString().back() ==
path_value.ToStringView().ends_with

anonrig · 2024-07-15T12:02:31Z

+ // Check if the path has a trailing slash. If so, add it after
+ // ToNamespacedPath() as it will be deleted by ToNamespacedPath()
+ bool slashCheck = !path_value.ToString().empty() &&
+ path_value.ToString().back() ==


anonrig · 2024-07-15T14:42:36Z

 bool slashCheck = !path_value.ToString().empty() &&
- path_value.ToString().back() ==
- std::filesystem::path::preferred_separator;
+ path_value.ToStringView().ends_with(


The previous line is not needed path_value.ToString() creates an unnecessary string.
Can you also remove this in other places?

huseyinacacak-janea · 2024-07-26T06:31:22Z

I've fixed the suggestions. Is there anything else I can do to help this PR move forward?

QuantumQuin · 2024-08-07T15:07:41Z

@anonrig Is there anything else we can do to help this PR move forward? I'm having many issues with long paths on Windows and am eager to get this fixed.

nodejs-github-bot · 2024-08-07T15:15:34Z

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

nodejs-github-bot · 2024-08-08T07:07:44Z

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

nodejs-github-bot · 2024-08-08T10:02:39Z

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

huseyinacacak-janea · 2024-08-09T05:36:22Z

The failing test in the CI is a known flaky test.

nodejs-github-bot · 2024-08-09T12:34:37Z

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

nodejs-github-bot · 2024-08-10T14:12:55Z

Landed in 37f9eca

PR-URL: #53294Fixes: #50753 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>

nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. fs Issues and PRs related to the fs subsystem / file system. needs-ci PRs that need a full CI run. labels Jun 3, 2024

huseyinacacak-janea force-pushed the huseyin-11801-long-path-error branch from 3ee742c to 27a4505Compare June 3, 2024 12:11

H4ad previously approved these changes Jun 3, 2024
View reviewed changes

StefanStojanovic added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 3, 2024

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 3, 2024

anonrig requested changes Jun 3, 2024
View reviewed changes

huseyinacacak-janea force-pushed the huseyin-11801-long-path-error branch from 27a4505 to 42b88bfCompare July 1, 2024 09:31

module,win: fix long path resolve
14a1de0

huseyinacacak-janea force-pushed the huseyin-11801-long-path-error branch from 42b88bf to 14a1de0Compare July 2, 2024 05:37

StefanStojanovic added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 2, 2024

H4ad approved these changes Jul 2, 2024
View reviewed changes

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 3, 2024

H4ad requested a review from anonrig July 15, 2024 12:01

anonrig reviewed Jul 15, 2024
View reviewed changes

fixup! module,win: fix long path resolve
dae0bfe

anonrig reviewed Jul 15, 2024
View reviewed changes

Comment threadsrc/node_file.cc

fixup! module,win: fix long path resolve
0e2c739

anonrig approved these changes Aug 7, 2024
View reviewed changes

anonrig added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 7, 2024

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 7, 2024

H4ad added commit-queue Add this label to land a pull request using GitHub Actions. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. labels Aug 10, 2024

nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 10, 2024

nodejs-github-bot merged commit 37f9eca into nodejs:mainAug 10, 2024

targos pushed a commit that referenced this pull request Aug 14, 2024
module,win: fix long path resolve
e676d98
PR-URL: #53294Fixes: #50753 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>

RafaelGSS mentioned this pull request Aug 19, 2024
v22.7.0 proposal #54452
Merged

This was referenced Sep 9, 2024
Upgrade to Node.js 22.7.0 karlhorky/node-js-max_path-windows-bug#2
Open
Long node_modules paths cannot be found on Windows when LongPathsEnabled enabled #50753
Closed

BalaM314 mentioned this pull request Sep 19, 2024
Node does not determine that a file is an ES module when the package.json is in a long path #54304
Closed

targos added the dont-land-on-v20.x label Sep 21, 2024

joyeecheung mentioned this pull request Jan 23, 2025
[v20.x backport] src: move package_json_reader cache to c++ #56590
Closed

wonu mentioned this pull request Feb 28, 2026
Subpath imports (#) fail on Windows when package.json path >= 260 chars (MAX_PATH) #62043
Closed

	env->isolate(), file_path.c_str(), strlen(file_path.c_str()))
	env->isolate(), file_path.c_str(), file_path.size())

	path_value.ToString().back() ==
	path_value.ToStringView().ends_with

Uh oh!

Uh oh!

Conversation

huseyinacacak-janea commented Jun 3, 2024

Uh oh!

targos commented Jun 3, 2024

Uh oh!

H4ad commented Jun 3, 2024

Uh oh!

nodejs-github-bot commented Jun 3, 2024

Uh oh!

anonrig left a comment

Choose a reason for hiding this comment

Uh oh!

MoLow commented Jun 3, 2024

Uh oh!

nodejs-github-bot commented Jun 4, 2024

Uh oh!

huseyinacacak-janea commented Jun 5, 2024

Uh oh!

nodejs-github-bot commented Jul 4, 2024

Uh oh!

huseyinacacak-janea commented Jul 5, 2024

Uh oh!

huseyinacacak-janea commented Jul 15, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

huseyinacacak-janea commented Jul 26, 2024

Uh oh!

QuantumQuin commented Aug 7, 2024

Uh oh!

nodejs-github-bot commented Aug 7, 2024

Uh oh!

nodejs-github-bot commented Aug 8, 2024

Uh oh!

nodejs-github-bot commented Aug 8, 2024

Uh oh!

huseyinacacak-janea commented Aug 9, 2024

Uh oh!

nodejs-github-bot commented Aug 9, 2024

Uh oh!

nodejs-github-bot commented Aug 10, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants