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

@wynd/wynd-script

v1.6.1

Published

List of various useful Javascript related scripts compiled in one repository

Downloads

4

Readme

Wynd Script

List of various useful Javascript related scripts compiled in one repository.

Usage

yarn add -D @wynd/wynd-script
# or
yarn --global add -D @wynd/wynd-script # deprecated

Then use the command as follow in you project root:

./node_modules/.bin/wsc

or through your package.json scripts with: wsc <command> [options]

Options list

  • -p or --project: [default: ./package.json] - specify the package json file to use

Command list

  • wsc diffTslint [./tslint.json]: expose a diff between you tslint.json file and alors tslint config rules that your config extends. It helps for deduping and cleaning tslint config files.

  • wsc pub [--no-build] [--npm] [--public]: publish your package on "@latest" npm tag relatively to your version. Make sure to be logged once with npm and yarn to your registry. If --no-build is specified, no yarn build command will be called. By default, yarn client will be used to publish, you can set --npm to use npm instead. :warning: In npm mode, when publishing a scoped package, npm will use .npmrc registry option before cli flag or package.json publishConfig object. In case of scopped package, you can also provide the --public flag if you want to publish it with a public access.

  • wsc pub:dev [--no-build]: like the command before but on "@next" npm tag. The version used is computed to be like <your version patch bumped>-dev.x (e.g. if your on version 1.0.0, the next version will be 1.0.1-dev.0 then dev.1 and so on).

  • wsc pub:rc [--no-build]: like the command before but on "@rc" npm tag. The version used is computed to be like <your version patch bumped>-rc.x (e.g. if your on version 1.0.0, the next version will be 1.0.1-rc.0 then rc.1 and so on).

  • wsc syncPeer: it will modify your package json file to synchronize your peerDependencies with your devDependencies. It can be set to the postinstall and postupdate npm hooks.

  • wsc pack: it will generate a "tgz" file for your module. For dev purposes, you should handle the "build" step by your. (e.g. if you need to build in debug mode)

  • wsc coverage: reveal the coverage average (line, statements, functions, branches) :warning: your coverageReporters must be setup with json-summary.


:warning: Only for gitlab-ci usage. you have to declare in gitlab's var : CI_API_URL( gitlab api url ) and GITLAB_API_READ_ONLY_TOKEN( gitlab private access token ).

  • wsc compareCoverage [--ref] [--threshold]: compare your current average from the last merge request average merged on --ref branch. --ref default value is develop. --threshold is the percent delta authorized between your ref branch and your current coverage. --threshold default value is 0. :warning: your coverageReporters must be setup with json-summary.

License

MIT