npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ci-yarn-upgrade

v0.7.6

Published

Keep NPM dependencies up-to-date with CI, providing version-to-version diff for each library

Downloads

113

Readme

ci-yarn-upgrade CircleCI

This command keeps npm dependencies up-to-date by making pull requests from CI.

ci-yarn-upgrade

This is inspired by bitjourney/ci-npm-update.

Installation

yarn global add ci-yarn-upgrade

Usage

Setting Environment Variables to CircleCI

You can add environment variables using the Project settings > Environment Variables page of your project.

  • You should set GITHUB_ACCESS_TOKEN
  • You may set GIT_USER_NAME and GIT_USER_EMAIL
    • this appliction uses GIT_USER_NAME and GIT_USER_EMAIL for commit

Add DeployKey to GitHub from CircleCI

this command is pushing from build, so you should add read/write deployment key at Project settings > Checkout SSH keys page of your project.

Configure circle.yml

our complete example is here.

Use official Node image

Official Node image contains yarn command now.

docker:
  - image: node:10-alpine

Install git with SSH

Because ci-yarn-upgrade uses newer git feature.

run: apk add --update --no-cache git openssh-client

Configure Scheduling build

In the example below, the scheculed-upgrade workflow is configured to run every wednesday at 13:00pm UTC.

jobs:
  yarn-upgrade:
    docker:
      - image: node:10-alpine
    steps:
      - run: apk add --update --no-cache git openssh-client
      - checkout
      - run: yarn global add ci-yarn-upgrade
      - run: yarn install
      - run: ci-yarn-upgrade --execute --verbose;
workflows:
  version: 2
  scheculed-upgrade:
    triggers:
      - schedule:
          cron: "0 13 * * 3"
          filters:
            branches:
              only:
                - master
    jobs:
      - yarn-upgrade

Command Behavior

By default, ci-yarn-upgrade runs in dry-run mode.

ci-yarn-upgrade

this command works locally and output result to standard output.

dry-run

execution

ci-yarn-upgrade --execute

if you set --execute, this command push branch to remote, and make a pull request.

CLI options

Usage: ci-yarn-upgrade [options]

Keep NPM dependencies up-to-date with CI, providing version-to-version diff for each library

Options:

  -h, --help                   output usage information
  -V, --version                output the version number
  -n, --username <username>    specify the commit auther name. You may set GIT_USER_NAME to environment variable.
  -e, --useremail <useremail>  specify the commit auther email. You may set GIT_USER_EMAIL to environment variable.
  -t, --token <token>          specify personal access token for GitHub. use only for debugging purpose. You should set GITHUB_ACCESS_TOKEN to environment variable.
  --execute                    if you don't specify this option, allows you to test this application.
  -L, --latest                 if you specify this option, upgrades packages ignores the version range specified in package.json
  -v, --verbose                shows details about the running ci-yarn-upgrade
  -k, --keep                   if you specify this option, keep working branch after all.
  --prefix <prefix>            specify working branch prefix. default prefix is "yarn-upgrade/"
  --workingdir <path>          specify project root dir. it contains package.json. default path is /path/to/myproject
  --with-shadows               if you specify this option, shows shadow dependencies changes.

Development

Setup

git clone https://github.com/taichi/ci-yarn-upgrade
cd ci-yarn-upgrade
yarn install

License

Copyright 2016 taichi

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.