# vue-cli-plugin-pristine

> Pristine for vue-cli

Latest version **1.0.3** (published 2019-11-30) · MIT license · 0 weekly downloads

## Install

```sh
npm install vue-cli-plugin-pristine
pnpm add vue-cli-plugin-pristine
yarn add vue-cli-plugin-pristine
bun add vue-cli-plugin-pristine
```

## Health

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

Positive: no vulnerabilities.

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

Negative: abandoned.

## Facts

| | |
|---|---|
| Version | 1.0.3 |
| Published | 2019-11-30 |
| First published | 2019-11-09 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 56.1 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Author | Luke Williams |
| Maintainers | iquidus |

## Links

- npm: https://www.npmjs.com/package/vue-cli-plugin-pristine
- Repository: https://github.com/octanolabs/vue-cli-plugin-pristine
- Homepage: https://github.com/octanolabs/vue-cli-plugin-pristine#readme
- Issues: https://github.com/octanolabs/vue-cli-plugin-pristine/issues
- npm.io page: https://npm.io/package/vue-cli-plugin-pristine

## Recent versions

- 1.0.3 (latest) — 2019-11-30
- 1.0.2 — 2019-11-11
- 1.0.1 — 2019-11-10
- 1.0.0 — 2019-11-09

## README

# vue-cli-plugin-pristine
[![NPM version](https://img.shields.io/npm/v/vue-cli-plugin-pristine.svg?style=flat)](https://npmjs.com/package/vue-cli-plugin-pristine) [![NPM downloads](https://img.shields.io/npm/dm/vue-cli-plugin-pristine.svg?style=flat)](https://npmjs.com/package/vue-cli-plugin-pristine) [![CircleCI](https://circleci.com/gh/octanolabs/vue-cli-plugin-pristine/tree/master.svg?style=shield)](https://circleci.com/gh/octanolabs/vue-cli-plugin-pristine/tree/master)

Pristine project starter for vue-cli.

Inspired by [Pristine Typescript React](https://github.com/etclabscore/pristine-typescript-react).

## How to use Pristine in your vue-cli project

```
vue create myNewProject
cd ./myNewProject
vue add pristine
```

## Documentation Driven Development

There are many ways to drive open source development. Documenting the problem in the README gives a middle ground between technical and non-technical specifications. This allows organizing solutions to this challenge around community and documentation.

> [...] a beautifully crafted library with no documentation is also damn near worthless. If your software solves the wrong problem or nobody can figure out how to use it, there’s something very bad going on.

- [Readme Driven Development](http://tom.preston-werner.com/2010/08/23/readme-driven-development.html) by Tom Preson-Werner

### Conventions and Specifications

Pristine has some strong opinions built in like circleci, semantic-release, npm. So feel free to fork and change it at your own discretion. It is only meant to be a starting point. That being said:

Using conventions, documentation and specifications make it easier to:
- communicate the problem you are solving
- ease onboarding
- build and use composable tools
- promote open source contribution and engagement
- promote issue and feature discussion on Github itself

#### Resources

- [Pristine](https://github.com/etclabscore/pristine)
- [opensource.guide](https://opensource.guide/)
- [Github community profiles for public repositories](https://help.github.com/articles/about-community-profiles-for-public-repositories/)
- [Readme Driven Development](http://tom.preston-werner.com/2010/08/23/readme-driven-development.html)
- [pengwynn/flint](https://github.com/pengwynn/flint)
- [Working Backwards](https://www.allthingsdistributed.com/2006/11/working_backwards.html)
- [Literate programming](https://en.wikipedia.org/wiki/Literate_programming)
- [Hammock Driven Development](https://www.youtube.com/watch?v=f84n5oFoZBc)
- [Inversion and The Power of Avoiding Stupidity](https://fs.blog/2013/10/inversion/)
- [choosealicense.com](http://choosealicense.com)

## Getting Started

To get started, [fork](https://help.github.com/articles/fork-a-repo/) or [duplicate](https://help.github.com/articles/duplicating-a-repository/) the repository. Then edit this file and delete everything above this line.

Then edit the `package.json` and change the `name` and `homepage` fields to match your newly created repository.

### Contributing

How to contribute, build and release are outlined in [CONTRIBUTING.md](CONTRIBUTING.md), [BUILDING.md](BUILDING.md) and [RELEASING.md](RELEASING.md) respectively. Commits in this repository follow the [CONVENTIONAL_COMMITS.md](CONVENTIONAL_COMMITS.md) specification.

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