Use jsxc instead of commoner #2230
Closed
Conversation
This file contains hidden or 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
Contributor
|
👍 commoner seems to have more bugs than features in my experience. |
Member
There was a problem hiding this comment.
Doesn't optimist take care of outputting options/usage?
Contributor
Author
There was a problem hiding this comment.
You need to provide usage yourself. It does describe all of the options. I wanted to put some common use cases in here to make the tool more usable.
Collaborator
|
Should we switch to recommending |
Member
|
We're killing our tools so this is dead 💀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Noticed several bug reports in the past few days on IRC. Still think commoner is the wrong tool for this job and jsxc is the right one.
Test plan: tested jsxc using the normal test plan. Ran bin/jsx, behaved same as jsxc