Improved Deno CLI #742
Merged
Improved Deno CLI #742
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
|
LGTM! thanks @Kyiro |
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
|
Thank you for accepting 🙏 |
|
thank you 🙏 will deploy the patch later |
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.
I wanted to use the esm.sh CLI but noticed it had a few issues, so I decided to try and fix them myself.
importsproperty directly indeno.json, which has been the go-to for many since it has been introduced in Deno v1.30 (it should still support external import maps from my testing)deno fmtinstead of forcing 2 space indent