GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Regression in v20.4.0, some unicode characters no longer supported in file names · Issue #48813 · nodejs/node Closed Closed Copy link DescriptionVersionv20.4.0 PlatformWindows NT 10.0.19043.0 x64 Subsystemfs What steps will reproduce the bug?Code: const fs = require('fs'); const name = String.fromCodePoint(0x1F525); fs.writeFileSync(name, ''); Results: > node-v18.16.1 test.js > node-v20.4.0 test.js node:internal/fs/utils:351 throw err; ^ Error: ENOENT: no such file or directory, open '🔥' How often does it reproduce? Is there a required condition?Consistently. What is the expected behavior? Why is that the expected behavior?Create an empty file with the given name. What do you see instead?An error. Reacted by Alt Activity
MetadataMetadataAssigneesLabelsNo labels TypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |