Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove non-ASCII limitation #20

Merged
merged 5 commits into from Sep 27, 2022
Merged

Conversation

birjj
Copy link
Contributor

@birjj birjj commented Sep 26, 2022

Closes #19 (see that issue for more information)

I have been unable to find documentation for the non-ASCII limitation, and anecdotal testing has shown forward slashes to be supported in non-ASCII paths:

Screenshot of terminal showing Node.js reading file with non-ASCII path with both forward and backward slashes as seperator

This limitation has further caused issues in projects that rely on this, e.g. facebook/docusaurus#8124, gatsbyjs/gatsby#19600, and SAP/ui5-tooling#469, amongst others.

Fixes sindresorhus#19
I have been unable to find documentation for the non-ASCII limitation,
and anecdotal testing have shown forward slashes to be supported in
non-ASCII paths. See sindresorhus#19 for more information
@sindresorhus sindresorhus merged commit b83ed2a into sindresorhus:main Sep 27, 2022
@sindresorhus
Copy link
Owner

Makes sense. I cannot find any references to it anymore either.

birjj added a commit to birjj/docusaurus that referenced this pull request Sep 27, 2022
See sindresorhus/slash#19 for discussion on limitation in the originating package
This updates the integrated function to match sindresorhus/slash after sindresorhus/slash#20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support non-ASCII characters in paths
2 participants