Skip to content

Cli's build command always prompts for package #195

@tyler-dane

Description

@tyler-dane

Where did this happen?

Local code with an up-to-date main branch

Expected Behavior

When running yarn cli build web, I shouldn't be prompted for which package to build. Instead, the CLI will automaticlaly build the web package.

All of these commands work as expected:

yarn cli build web -e staging                                # build web for staging env
yarn cli build web -e production                          # build web for production env
yarn cli build web --environment=production    # same as ^
yarn cli build web --clientId=foo                          # build web with clientId of 'foo' 
yarn cli build nodePckgs                                       # build node package

Current Behavior

The CLI still prompts for the package to build

Steps to Reproduce

Run yarn cli build web or any combination of yarn cli build web [options].

Possible Solution

Fix the arg parsing so that the package is successfully interpreted before continuing the script

Context

This makes it more difficult for users to use the CLI

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions