Skip to content

Latest commit

 

History

History
150 lines (112 loc) · 4.29 KB

CONTRIBUTING.md

File metadata and controls

150 lines (112 loc) · 4.29 KB
Raw

Contributing to CSSTools Plugins

You want to help? You rock! Now, take a moment to be sure your contributions make sense to everyone else.

Reporting Issues

Found a problem? Want a new feature?

Remember, a bug is a demonstrable problem caused by our code.

If this guide itself is not working or is not clear, please report it.

Project setup

If you do need to set the project up locally yourself, feel free to follow these instructions:

System Requirements

Submitting Pull Requests

Pull requests are the greatest contributions, so be sure they are focused in scope and avoid unrelated commits.

  1. To begin; fork this project, clone your fork, and add our upstream.

    # Clone your fork of the repo into the current directory
git clone https://github.com/<YOUR_USER>/postcss-plugins.git

# Navigate to the newly cloned directory
cd postcss-plugins

# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/csstools/postcss-plugins.git

  2. Where are you contributing?

  • If you want to contribute to plugins, plugin-packs or the CLI, run the following command:

     # Install and build the needed things to start local development
 # This also does an initial test of everything.
 # If this gives errors please open an issue so that we can look into it.
 npm run get-me-going

  • If you want to contribute to sites, you need to run the following command:

     cd sites
 # Install the needed things to start local development
 # If this gives errors please open an issue so that we can look into it.
 npm run get-me-going

  1. Create a branch for your feature or fix:

    # Move into a new branch for your feature
git checkout -b feature/thing
    # Move into a new branch for your fix
git checkout -b fix/something

  2. Navigate to the plugin you want to contribute to.

    # Navigate to a plugin directory
cd plugins/<plugin-name>
    # Navigate to the postcss-preset-env directory
cd plugin-packs/postcss-preset-env

  3. If your code follows our practices, then push your feature branch:

    # Run the linter
npm run lint
# Test current code
npm run build && npm run test
    # Push the branch for your new feature
git push origin feature/thing
    # Or, push the branch for your update
git push origin update/something

That’s it! Now open a pull request with a clear title and description.

Creating a new plugin here

  • Follow the guide for submitting a pull request
  • Run npm run get-me-going if you want to start local development.
  • Run npm run new-plugin to create a new plugin.
npm run new-plugin

A plugin name must be provided:
  new-plugin <human readable name>
  new-plugin Cascade Layers
npm run new-plugin Cascade Layers

- Creating new plugin Cascade Layers
- Copied base plugin to ./plugins/postcss-cascade-layers
- Cleaned up files and directories not required in a new plugin
- Relabeled references to base plugin
- Updated "package.json"

Done! 🎉

Your next steps:
- Run : "npm install" from the root directory
- Run : "cd plugins/postcss-cascade-layers"
- Run : "npm run build" to build your plugin
- Run : "npm run test" to test your plugin
- Run : "npm run test:rewrite-expects" to update test expects

Change "blue" to "purple" in "src/index.ts" and see how it affects the test outcome

Trouble shooting

This is a mono repo that contains unpublished packages. If you get warning about missing files, modules, packages you should do :

  • npm install -> get public dependencies
  • npm run build -> build private dependencies

if your issues is not mentioned here please open an issue so that we can extend the guides