# polyutil

> this is a npm polymer util to build polymer components and release them

Latest version **1.0.3** (published 2016-02-24) · ISC license · 0 weekly downloads

## Install

```sh
npm install polyutil
pnpm add polyutil
yarn add polyutil
bun add polyutil
```

Provides the command `polyutil`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.3 |
| Published | 2016-02-24 |
| First published | 2016-02-24 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 12 |
| Known vulnerabilities | 0 (+10 in 4 direct dependencies) |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Fahim Chowdhury |
| Maintainers | fahimchowdhury |
| Keywords | polymer, utils, polymerextend |

## Links

- npm: https://www.npmjs.com/package/polyutil
- Repository: https://github.com/fahimc/polyutil
- Issues: https://github.com/fahimc/polyutil/issues
- npm.io page: https://npm.io/package/polyutil

## Dependencies (12)

- [open](https://npm.io/package/open.md) ^0.0.5
- [grunt](https://npm.io/package/grunt.md) ^0.4.5
- [express](https://npm.io/package/express.md) ^3.4.8
- [shelljs](https://npm.io/package/shelljs.md) ^0.6.0
- [body-parser](https://npm.io/package/body-parser.md) ^1.14.2
- [grunt-eslint](https://npm.io/package/grunt-eslint.md) ^17.1.0
- [grunt-confirm](https://npm.io/package/grunt-confirm.md) ^1.0.2
- [grunt-replace](https://npm.io/package/grunt-replace.md) ^0.10.2
- [method-override](https://npm.io/package/method-override.md) ^2.3.5
- [grunt-shell-spawn](https://npm.io/package/grunt-shell-spawn.md) ^0.3.9
- [grunt-contrib-copy](https://npm.io/package/grunt-contrib-copy.md) ^0.8.1
- [grunt-contrib-clean](https://npm.io/package/grunt-contrib-clean.md) ^0.6.0

## Recent versions

- 1.0.3 (latest) — 2016-02-24
- 1.0.0 — 2016-02-24

## README

#polyutil
This is an npm polymer util to build polymer components and release them.

When building polymer components you can encapsulate your project within itself which means your references to bower components can be internal rather than pointing out of the project folder. This is what is required when you release the component but it can be a pain to maintain when developing.

Polyutil will convert all the bower_component references to point outwards upon release.

##Component Setup
You will need two branches `master` and `release` in your repo. Your repo will need to be a git repo. 

##polyutil serve

This will create and launch a web server  

##polyutil release

This will merge your master branch with the release branch and convert all the bower_components references to point outward and push all the changes and finally create a new tag.

---
_Source: https://npm.io/package/polyutil · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._