chenasraf / massarg

Command and argument parser on steroids - JS/TS

Hi 👋, I'm Chen Asraf 🇮🇱

I make fully fledged, production-ready systems for start-ups and businesses. Also apps & others as hobbies :)

Contact me for availability at [email protected]

---

I do my best to create useful programs, apps, and tools; and support open source. If you are feeling incredibly generous and want to help sustain my projects, please consider donating :) I will really appreciate it!

A little about me

• 💻 In my personal time, I'm working on Dungeon Paper, a free Android/iOS app for Dungeon World players and DMs
• 🥋 Check out my repositories for some more of my open source projects
• 💭 My dream is to make my own game development studio, and make a successful and fun game - my passion project 🎮
• 💪🏼 I’m proficient in TypeScript, React, Flutter/Dart, and I love trying out new technologies and languages.
• 👌🏼 I'm also familiar with Python, Vue, and fiddle with Ruby, Node.js, and many others
• 👯 I’m looking to collaborate on cool open source projects :)

Projects

Because you can only have 6 pins.

NPM

• Simple Scaffold - Generate any file structure - from single components to entire app boilerplates, with a single command.
• Massarg - Flexible, powerful, and simple command/argument parser for CLI applications

Dart/Flutter

Apps

• Dungeon Paper - A Dungeon World character sheet app written with Flutter
• Mudblock - An MUD client for mobile & desktop

Packages

• Script Runner - Run all your project-related scripts in a portable, simple config.
• Unaconfig - Load your user's config files for your package easily, from multiple sources & formats. Like cosmiconfig, but for Dart!
• CTelnet - A simple Telnet client for Dart/Flutter, parse incoming and outgoing data easily and quickly.
• btool - Generic build helper tools for Flutter/Dart such as manipulating version, package name or application ID
• Wheel Spinner - A simple Flutter widget for updating a number using a pitch bender-like spinner

Neovim

• text-transform.nvim - Common text transformers for nvim - switch between camelCase, PascalCase, snake_case, and more!

Rust

• tblf - Turns any CLI output lines into tables.

Go

• GI Gen - Gitignore generator for any type of project

GitHub Stats

   

Find me elsewhere:

I mostly use:

I sometimes use:

massarg's Issues

Slice argv

process.argv is usually sliced from 2, we already allow to override it

`example` output should not be required

When omitted, the output line should not be displayed

Better `required` error message

Current:

{option} is required, but was not defined for {command}

Desired:

Option: `{option}` is required, but was not defined for command: `{command}`. Try using`--{option} {value}`

`Options` type should not require `help` & `extras`

Options type should not require help & extras, but only enrich the options when appropriate instead

Before version 1.0

• Tests
• Take nameless args (multi/one)
• Add "required" option (should work properly with commands option, so will only be required if using the same command
• Add "array" option for multiples
• Add default value to help text (with option to disable)
• automation
• Add example lines

v2.0

This is a master issue for tracking the 2.0 rewrite.

I plan to completely refactor everything and many interfaces will break. This is a significant update.

However, it comes to address several issues:

• Default option parsing is inconsistent
• Flags and arrays validation problems
• Overcomplicated code base with many patches to include new unplanned functionality
• It's not easy to code split & define groups or subcommands

The main tasks are listed below:

• Refactor main interfaces
  • Creation
  • Main
  • Subcommands
  • Options
  • Flags
  • Help
  • Example lines
  • Help
• Allow composition of commands & options in a hierarchy
• Remove bool options, introduce flags with negation instead
• Improve type inference and safety
• Easier & better assertions
• More control over help display & formatting
• Re-write tests and make sure to cover many cases

Bug fixes:

• Type mismatches for child args - need better inference

The automated release is failing 🚨

🚨 The automated release from the pre branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the pre branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀