fix(docs):Make the ts-migrate able to execute #202
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
The ts-migrate produced errors for npm or npx when used with run command as it didn't used the local or remote repository for execution.Fixed the problem using "npm exec" command which is used for running local scripts installed at dependency level.
|
asttle-vuram
approved these changes
Jul 6, 2023
asttle-vuram
reviewed
Jul 6, 2023
huynhdev24
approved these changes
Jul 31, 2023
|
I guess review must be done by a person with write access to make merging acceptable |
|
Thanks for this PR @Prakhargarg-2010196, I was stuck and puzzled about how to run the script until I found it. Would be great if the maintainers could get this merged. |
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.
The ts-migrate produced errors for npm or npx when used with run command as it didn't used the local or remote repository for execution.Fixed the problem using "npm exec" command which is used for running local scripts installed at dependency level.
This will fix issue #201 I guess.