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

fastlane-pem

v1.0.0

Published

node wrapper for ruby fastlane pem module

Downloads

348

Readme

fastlane-pem

NPM version Build Status Coverage Status

Node wrapper for Ruby Fastlane PEM module

example


var pem = require('fastlane-pem')

pem({user:'gege', output:'/'}, (err, result) => {
    console.log(`STDOUT:\n${result.stdout}`)
    console.log(`STDERR:\n${result.stderr}`)

    if (err) {
        if (err.killed) console.error(`Terminated: ${err.signal}`)
        if (err.code) console.error(`Exit Code: ${err.code}`)
        console.error(err.message)
})

api

pem([options], [cb])

pem accepts optional options and callback, see tables below for all possibilities.

PEM Options

|PEM Option |Example|Description|Command Executed| |-------------|-------|-----------|----------------| | identifier(string) | {identifier:'myapp'} | The bundle identifier of your app | -a {identifier} | | output(string) | { output: outputDirectoryPath } | generates the pem profile in a specific directory | -e {outputDirectoryPath} |
| user (string) | { user:username } | Your Apple ID Username | -u {user} | | p12Password(string) | { p12Password: 'password' } | The password that is used for your p12 file | -p {p12Password} | | pemName (string) | { pemName:'filename' } | The file name of the generated .pem file | -o {pemName} |
| teamId(string) | { teamId:'ekjo' } | The ID of your team if you're in multiple teams | -b {teamId} |
| teamName(string) | { teamName:'teamA' } | The name of your team if you're in multiple teams | -l {teamName} | development(boolean) | { development:true } | Renew the development push certificate instead of the production one | --development | | force (boolean) | { force:true } | Create a new push certificate, even if the current one is active for 30 more days | --force |
| generateP12 (boolean) | { generateP12:true } | Generate a p12 file additionally to a PEM file | --generate_p12 | |savePrivateKey (boolean) | { savePrivateKey:true } | Set to save the private RSA key | --s |

Runtime Options

|Runtime Option |Example|Description| |----------------|-------|-----------| |timeout (number)| { timeout:0 } | specify when to exit execution in case of error | |password (string)| {password:''} | app store password | |path (string)| {path:'/'} | path of directory where PEM executes|

install

With npm do:

npm install --save fastlane-pem

testing

npm test

coverage

npm run view-cover

This will output a textual coverage report.

npm run open-cover

This will open an HTML coverage report in the default browser.