npm.io
2.1.1 • Published 4 years ago

@bootcamp-project/postcss-config

Licence
MIT
Version
2.1.1
Deps
3
Size
22 kB
Vulns
0
Weekly
0

Ready-to-use PostCSS Configuration

with Autoprefixer support by default

About

Minimum Viable Product: What is what we want?

The creation and deployment of a centralized sharable configuration, with the most well-known best practice approaches.

  • What are the goals?
    • Automation of publishing, testing, linting and packaging with GitLab-CI
    • Provide understandable documentation for the use of the configuration
    • Test the return of the configuration with unit tests and the validation of the configuration structure with smoke tests.
    • For the greatest possible compatibility we provide TypeScript definitions
    • Use the unified ESLint and Prettier configuration for static analysis of the source code
    • Provide a uniform configuration for PostCSS and Autoprefixer for all builders and bundlers

Getting Started

Project Links

Installation
yarn add @bootcamp-project/postcss-config

or

npm install @bootcamp-project/postcss-config
Usage

See @bootcamp-project/postcss-config preselections

Best practice PostCSS Config Example
// postcss.config.js
'use strict';

const PrettierConfig = require('@bootcamp-project/postcss-config/postcss.config')
module.exports = PrettierConfig

️ Features ️

Built With
PostCSS Autoprefixer TypeScript tbcp
Acknowledgements

Thanks for these awesome resources that were used during the development of the Bootcamp: PostCSS Configuration:

Changelog

See CHANGELOG for more information.

Roadmap

See the open issues for a list of proposed features (and known issues).

Contribute

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

Please read the contribution guidelines first.

  1. Give us a star, it's really important!
  2. Fork the Project: (git clone https://gitlab.com/the-bootcamp-project/configurations/postcss.git)
  3. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  4. Commit your Changes (git commit -m 'Add some AmazingFeature')
  5. Push to the Branch (git push origin feature/AmazingFeature)
  6. Open a Pull Request

License

See LICENSE for more information.

Contact

Bootcamp contributors - contributors @ bootcamp-project .com

Keywords