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

set-env-to-github_env

v1.2.1

Published

A migration tools convert `::set-env` to $GITHUB_ENV on GitHub Actions.

Downloads

3

Readme

set-env-to-github_env Actions Status: test

A migration tools convert ::set-env to $GITHUB_ENV on GitHub Actions.

Supported Migration

  • [x] echo "::set-env name={name}::{value}"echo "{name}={value}" >> "$GITHUB_ENV"
  • [x] echo "::set-output name={name}::{value}"echo "{name}={value}" >> "$GITHUB_OUTPUT"
  • [x] echo "::save-state name={name}::{value}"echo "{name}={value}" >> "$GITHUB_STATE"

For more details, see GitHub blog and documentation.

TODO: This tool does not support ::add-path migration yet. If you are interesting in this, please see https://github.com/azu/set-env-to-github_env/issues/2

Install

Install with npm:

npm install set-env-to-github_env

or Just use npx command in project root directory.

npx set-env-to-github_env

Require: Node.js 14+

Usage

Run command in project root directory.

Usage
  $ set-env-to-github_env

Examples
  $ set-env-to-github_env
  # migration ./github/workflows/*.{yml,yaml}

Example

Before

name: test
on: [push, pull_request]
jobs:
  test:
    name: "Test"
    runs-on: ubuntu-18.04
    steps:
      - name: set env for prod
        if: github.ref == 'refs/heads/main'
        run: |
          echo "::set-env name=FILE_ID::${FILE_ID}"
          echo "::set-env name=BUCKET_NAME::${BUCKET_NAME}"
        env:
          FILE_ID: 123456789012
          BUCKET_NAME: deploy-prod

After

name: test
on: [push, pull_request]
jobs:
  test:
    name: "Test"
    runs-on: ubuntu-18.04
    steps:
      - name: set env for prod
        if: github.ref == 'refs/heads/main'
        run: |
          echo "FILE_ID=${FILE_ID}" >> "$GITHUB_ENV"
          echo "BUCKET_NAME=${BUCKET_NAME}" >> "$GITHUB_ENV"
        env:
          FILE_ID: 123456789012
          BUCKET_NAME: deploy-prod

Changelog

See Releases page.

Running tests

Install devDependencies and Run npm test:

npm test

Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, please create an issue.

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Author

License

MIT © azu