require fails on Windows when the resolved absolute path reaches 260 characters

[soyuta]

C:/
   tmp/
     test/
       init.luau
       imsooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooolong.luau

print(
	#"C:\\tmp\\test\\imsooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooolong.luau"
)

require(
	"@self/imsooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooolong"
)

> lute run init.luau
259
success

If I add one more "o" here, bringing the absolute path length to 260 characters, the following error occurs:

> lute run init.luau
260
error requiring module "@self/imsoooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooolong": could not resolve child component "imsoooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooolong"
stacktrace:
[C] function require
./init.luau:5

Since Lune doesn't have this issue, it doesn't seem to be a limitation of Luau itself. (Lune works fine even with paths over 500 characters long)

When using a package manager like pesde, it's fairly common for packages to use Git tree IDs as version IDs, so I've often run into cases where the absolute path exceeds 260 characters.

[Vighnesh-V]

Hey, apparently this is actually a restriction of the Win32 API - the MAX_PATH limit in windows is exactly 260, so when we resolve requires, I bet you we're calling some win32 api that blows up. As of windows 10 the restriction has been removed, so you could opt into long paths using the instructions here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry.

On our end, I think we can preface long paths with \?\ or something to that effect.