Each CI step currently runs yarn install. This should be cached using actions/cache so that we don't needlessly refetch packages and spend time preparing dependencies when they haven't changed.

As of now, we can CI failures, as soon as we wrote some code that just adds 0.1kB. It would be great to set a higher granularity. A few possible options:

1. Being able to set granularity to kB
2. Being able to set a "max higher" amount, which will end up in warnings

The reason we don't just increase the kB, is that it then says, that our bundle shrank, which is also not true.

I can't believe this doesn't have any stars yet!
This package does exactly what it should do - really awesome!

I was first a bit confused, that the config is not described anywhere, maybe you want to add a bit of docs for that.

But the fact, that I just do yarn packwatch and I'm done, is awesome.
Thanks!

It's been a while since Packwatch has been touched in any meaningful way, 2023 is time. 🚀

Open to feature requests

In mapping what v3 will look like and offer, the suggestion box is open! 🎉 Just post under this issue to start a discussion on features or changes you'd like to see in Packwatch 3.

Projected features

• Ability to have greater control of threshold that trigger failing checks (#18)
• Tracking the number of direct / transitive dependencies (via the Yarn API?)
• A versioned schema for packwatch.json

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update actions/cache action to v4
• chore(deps): update codecov/codecov-action action to v4
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): replace dependency rome with @biomejs/biome
• chore(deps): update dependency ts-jest to v29.1.4
• chore(deps): update jest monorepo to v29.5.12 (@types/jest, jest)
• chore(deps): update dependency @types/node to v18.19.33
• chore(deps): update dependency node to v18.20.3
• chore(deps): update dependency rome to v12.1.3
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency node to v20 (node, @types/node)
• chore(deps): update dependency typescript to v5
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

It's quite weird, that although the first run was successful, it exits with exit code 1.
As a user new to packwatch, I'm wondering what I did wrong.

It would be cool to leverage GH actions and archive historical Packwatch results based on commit hash in a dedicated git branch.
This would allow for really cool analysis over time and could open the door for a version of Packwatch that could live solely in CI.

🤔

There is no reason why anything devDependency should not just be merged as soon as it passes the build.

This can be done using the Treat approvals as requests to merge feature of Dbot combined with the auto-approve GH action.

🚨 The automated release from the master branch failed. 🚨

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

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 resolve 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 master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is 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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:%[email protected]/mcataford/packwatch.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀