| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Switching to import is good, but I think removing import/require is bad. Like I said, it's not clear where these methods from. When I first saw new URL('file:///C:/path/').pathname; // Incorrect: /C:/path/
fileURLToPath('file:///C:/path/'); // Correct: C:\path\ (Windows)I really don't know how to use fileURLToPath,
It doesn't make sense to remove these imports. check https://nodejs.org/api/child_process.html, every example has require('child_process') it's very clear how to use it. |
Sorry, something went wrong.
|
worker_threads /fs / assert/dns has those imports as well, I don't think people care much it's import or require |
Sorry, something went wrong.
|
Yes, with pleasure. |
Sorry, something went wrong.
PR-URL: #38651 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Masashi Hirano <shisama07@gmail.com>
PR-URL: #38651 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Masashi Hirano <shisama07@gmail.com>
| Back | FazBrowse Home | New Git URL |
Alternative to #38645, removing use of require or adding import equivalents where it makes sense.
@fisker what do you think?