yarnpkg/berry

[Bug]: When using Korean directory in Windows.The .pnp.cjs file cannot be found.

eungyeole opened this issue · 3 comments

Self-service

  • I'd be willing to implement a fix

Describe the bug

When using Korean directory in Windows.The pnp.js file cannot be found.
I tested both the MAC environment and the window environment.
However, this phenomenon seemed to appear only in windows.
I guess it doesn't understand the letters in UTF8 format.
I hope it helps solve the bug.

Error Message

internal/modules/cjs/loader.js:979
  throw err;
  ^

Error: Cannot find module 'C:\Users\alpspaca\�ѱ��׽�Ʈ\.pnp.cjs'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:976:15)
    at Function.Module._load (internal/modules/cjs/loader.js:859:27)
    at Module.require (internal/modules/cjs/loader.js:1036:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1292:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:448:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:71:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}

To reproduce

code url:
https://github.com/eungyeole/berry-utf8-error

image

Environment

System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
  Binaries:
    Node: 13.11.0 - ~\AppData\Local\Temp\xfs-c99e5c16\node.CMD
    npm: 6.13.7 - D:\nodejs\npm.CMD

Additional context

No response

@merceyz
I'm sorry .
I think I've become a better person thanks to you.
I fixed it. Don't you need anything else?

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟