You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have multiple packages in one repo you can either have all of them reported as one (packages/*/dist/*.js), or only one reported (packages/pkg-one/dist/*.js).
Running the script multiple times overrides the last report each time.
What is the expected behavior?
CLI
My proposal is to add a new argument to the CLI: --name or --package. Using this would tag the report as being for a specific package, separating it from the others.
This would allow for running the script multiple times for reporting multiple packages.
Server
This can be stored in various ways, but the simplest one would be to simply add a package field to the report, and when returning the results from an endpoint simply return all the commitSha+package combos.
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
If you have multiple packages in one repo you can either have all of them reported as one (
packages/*/dist/*.js
), or only one reported (packages/pkg-one/dist/*.js
).Running the script multiple times overrides the last report each time.
What is the expected behavior?
CLI
My proposal is to add a new argument to the CLI:
--name
or--package
. Using this would tag the report as being for a specific package, separating it from the others.This would allow for running the script multiple times for reporting multiple packages.
Server
This can be stored in various ways, but the simplest one would be to simply add a
package
field to the report, and when returning the results from an endpoint simply return all thecommitSha+package
combos.e.g.
If this is a feature request, what is motivation or use case for changing the behavior?
It's impossible to use this service in a monorepo. It would allow projects that use it (popular ones include Vue, babel) to do so.
The text was updated successfully, but these errors were encountered: