Skip to content

util: parseArgs instead of string and boolean should handle all primitive data types  #44484

@ErickWendel

Description

@ErickWendel

What is the problem this feature will solve?

In today's @nodejs/tooling WG meeting, we're discussing the parseArgs that the config supports only either boolean or string for parsing args.

nodejs/tooling#155

What is the feature you are proposing to solve the problem?

I'd like to open for discussion on whether we should support other primitive types such as numbers and complex types such as Streams.

There're some concerns about it but I think it will be worth it to hear what other people think about it

What alternatives have you considered?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues that request new features to be added to Node.js.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions