Print output while publishing?

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
cli, release

Research direction

Start by tracing the publishing flow after the "ok to publish?" prompt and locate where each package is sent through npm publish. Define what progress feedback should look like during a multi-package publish, then verify that the chosen behavior makes the process visibly active without producing misleading output.

Written by the indexing model from the issue text.

Description

Currently, when publishing a monorepo with many packages it seems "hung" after the "ok to publish?" prompt. The main reason for that is that we are actively npm publishing each of the packages, but without any feedback it is easy to seem like nothing is going on and the process is therefore hung.

I'm not sure exactly what we should do here, as I don't think that automatically emitting "published x" is necessarily better either...

Dominant language
JavaScript
Stars
71
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from release-it-plugins/workspaces

All issues in release-it-plugins/workspaces

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.