Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postcss/postcss
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 558bc79
Choose a base ref
...
head repository: postcss/postcss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fcaf73c
Choose a head ref
  • 8 commits
  • 9 files changed
  • 6 contributors

Commits on Jun 16, 2019

  1. Add postcss-simple-trig to list (#1279)

    @Rplus @ai
    Rplus authored and ai committed Jun 16, 2019
    Configuration menu
    Copy the full SHA
    fbcb35a View commit details
    Browse the repository at this point in the history

Commits on Jul 17, 2019

  1. Update README.md claim of "perfect" Parcel support (#1286) 

    * Fix README.md claim of "perfect" Parcel support

Update `README.md` to not tout Parcel's implementation as "perfect". There are [the several issues in Version 1](https://github.com/parcel-bundler/parcel/labels/CSS%20Preprocessing). And [Version 2](https://github.com/parcel-bundler/parcel/projects/5) is not out yet to [possibly fix the issues via [issue #2157](parcel-bundler/parcel#2157).

I am amenable to any alteration of this edit. Perhaps, the change should be _only_ to remove the word "perfect". But, Parcel's implementation has been flawed for a long time.

_I provide the extra information, in hopes of saving someone else from believing Parcel will manage PostCSS for them. Three times over this and the past years, I have crawled out of the maze of Parcel & PostCSS rabbit holes to decide that it is _still_ better for a project to process with PostCSS directly, independently of Parcel._

* Fix README.md grammar in previous edit

I fixed grammatical errors that I made in my previous edit of the README.md.
    @wesleyboar @ai
    wesleyboar authored and ai committed Jul 17, 2019
    Configuration menu
    Copy the full SHA
    e03abd6 View commit details
    Browse the repository at this point in the history

  2. Remove removed word

    @ai
    ai committed Jul 17, 2019
    Configuration menu
    Copy the full SHA
    f736120 View commit details
    Browse the repository at this point in the history

Commits on Aug 5, 2019

  1. chore(ci): add node 12 and remove node 11 in ci (#1288) 

    * Update dependencies

* chore(ci): add node 12 and remove node 11 in ci
    @chiawendt @ai
    chiawendt authored and ai committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    a6abecc View commit details
    Browse the repository at this point in the history

  2. Use latest Node

    @ai
    ai committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    015d8b6 View commit details
    Browse the repository at this point in the history

Commits on Aug 21, 2019

  1. Add postcss-safe-area plugin. (#1290) 

    * Add postcss-safe-area plugin.

* Fix Travis typo checking and missing link
    @plegner @ai
    plegner authored and ai committed Aug 21, 2019
    Configuration menu
    Copy the full SHA
    2625a71 View commit details
    Browse the repository at this point in the history

Commits on Sep 5, 2019

  1. fix(types): return Warning[] from warnings() (#1292) 

    https://api.postcss.org/Result.html#warnings
https://api.postcss.org/LazyResult.html#warnings
    @buschtoens @ai
    buschtoens authored and ai committed Sep 5, 2019
    Configuration menu
    Copy the full SHA
    7520a71 View commit details
    Browse the repository at this point in the history

  2. Release 7.0.18 version

    @ai
    ai committed Sep 5, 2019
    Configuration menu
    Copy the full SHA
    fcaf73c View commit details
    Browse the repository at this point in the history
Loading