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: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.0.9
Choose a base ref
...
head repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.0.10
Choose a head ref
  • 7 commits
  • 11 files changed
  • 4 contributors

Commits on Jan 4, 2022

  1. Allow all classes for @apply (#6580) 

    * Always include css with apply in context

* Use let

We use it more consistently

* Remove early return

To match the style of the surrounding code

* Don't return layer directives

They do not need to be returned here. If it's needed in the future its easy enough to add it back.

* Use let

* Update changelog

* fix typo

And re-format comments

Co-authored-by: Jordan Pittman <[email protected]>
Co-authored-by: Robin Malfait <[email protected]>
    @garymathews @thecrypticace @RobinMalfait
    3 people authored Jan 4, 2022
    Configuration menu
    Copy the full SHA
    722232c View commit details
    Browse the repository at this point in the history

  2. Avoid writing to output files when no changes (#6550) 

    * fix(cli): avoid write same output when no changes

* generalize outputFile

This function will check a cache, it will only write the file if:
- The modified timestamps changed since last time we wrote something.
  This is useful to know if something changed by another tool or
  manually without diffing the full file.
- The contents changed.

* further simplify checks

Turns out that reading files and comparing them is fairly fast and there
is no huge benefit over only using the Stats of the file and keeping
track of that information.

Thanks @kentcdodds!

Co-authored-by: Robin Malfait <[email protected]>
    @g3offrey @RobinMalfait
    g3offrey and RobinMalfait authored Jan 4, 2022
    Configuration menu
    Copy the full SHA
    0bcd628 View commit details
    Browse the repository at this point in the history

  3. update changelog

    @RobinMalfait
    RobinMalfait committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    41e32bd View commit details
    Browse the repository at this point in the history

  4. Emit defaults from apply in css modules (#6875) 

    * Emit defaults from apply in css modules

* Update changelog
    @thecrypticace
    thecrypticace authored Jan 4, 2022
    Configuration menu
    Copy the full SHA
    058a925 View commit details
    Browse the repository at this point in the history

  5. Allow piping data into the CLI (#6876) 

    * use outputFile instead of direct writeFile

This is an improvement we introduced earlier but forgot this part.

* allow to pipe in data to the CLI

* add integration tests to validate piping to the CLI

* update changelog
    @RobinMalfait
    RobinMalfait authored Jan 4, 2022
    Configuration menu
    Copy the full SHA
    657bf5f View commit details
    Browse the repository at this point in the history

  6. update changelog

    @RobinMalfait
    RobinMalfait committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    83852dc View commit details
    Browse the repository at this point in the history

  7. 3.0.10

    @RobinMalfait
    RobinMalfait committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    30ea5b1 View commit details
    Browse the repository at this point in the history
Loading