Use path, fs from @types/node #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deribaucourt
approved these changes
Oct 13, 2023
idillon-sfl
requested changes
Oct 13, 2023
WilsonZiweiWang
force-pushed
the
Use-types-node
branch
from
ba6c1ea
to
d569e00
Compare
WilsonZiweiWang
changed the title
idillon-sfl
approved these changes
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seems like the files automatically include the
pathandfsfrom@types/nodeat rootpackage.json. So I don't think the obsolete ones from serverpackage.jsonare actually used.However, I didn't find a good replacement forfind, so I used thereaddirfromfsto achieve the similar results.