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.4.13
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.4.17
Choose a head ref
  • 16 commits
  • 50 files changed
  • 7 contributors

Commits on Oct 9, 2024

  1. Don't set display: none on elements that use hidden="until-found" (

    …#14625)
    
    Fixes an issue reported by the React Aria Components team here:
    
    adobe/react-spectrum#7160
    
    Basically `hidden="until-found"` behaves very differently than `hidden`
    and doesn't actually use `display: none`, so we don't want to apply the
    behavior we apply for the regular `hidden` attribute.
    
    ---------
    
    Co-authored-by: Robin Malfait <[email protected]>
    adamwathan and RobinMalfait authored Oct 9, 2024
    Configuration menu
    Copy the full SHA
    b570e2b View commit details
    Browse the repository at this point in the history

Commits on Oct 15, 2024

  1. 3.4.14

    RobinMalfait committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    c616fb9 View commit details
    Browse the repository at this point in the history

Commits on Oct 17, 2024

  1. Bump dependencies to fix vulnerabilities (#14697)

    This PR fixes some package vulnerabilities that you will see when
    running `npm install`. This PR fixes that by bumping dependencies to get
    rid of the vulnerabilities.
    RobinMalfait authored Oct 17, 2024
    Configuration menu
    Copy the full SHA
    c8c3a22 View commit details
    Browse the repository at this point in the history
  2. Add CODEOWNERS file (#14702)

    This PR adds a new `CODEOWNERS` file so that the
    `@tailwindlabs/engineering` will be automatically requested for review
    when changes are made to the repository.
    RobinMalfait authored Oct 17, 2024
    Configuration menu
    Copy the full SHA
    825cd83 View commit details
    Browse the repository at this point in the history
  3. update changelog

    RobinMalfait committed Oct 17, 2024
    Configuration menu
    Copy the full SHA
    8b41e82 View commit details
    Browse the repository at this point in the history

Commits on Nov 7, 2024

  1. Fix config types for boxShadow (#14856)

    `boxShadow` accepts multiple shadows just like `dropShadow` does. This
    patch fixes the TS typings to reflect that.
    
    See demo showing that multiple shadows are supported (complete with it
    incorrectly complaining that the config is bad) here:
    https://play.tailwindcss.com/VHqWbbEIrz?file=config
    
    ---------
    
    Co-authored-by: Philipp Spiess <[email protected]>
    tremby and philipp-spiess authored Nov 7, 2024
    Configuration menu
    Copy the full SHA
    4de0769 View commit details
    Browse the repository at this point in the history

Commits on Nov 14, 2024

  1. Add variable fallback to fix Chrome issue (#15003)

    This works around an issue in Chrome where `::selection` does not read
    from variables defined on `::selection` thus breaking all uses of color
    utilities with the selection variant. e.g. `selection::bg-red-200`.
    
    We now add a fallback value of `1` to all uses of
    `var(--tw-bg-opacity)`, `var(--tw-text-opacity)`,
    `var(--tw-border-opacity)`, etc… since Chrome treats the variable as if
    it did not exist because it's not defined on the parent.
    
    In Chrome 131 (until the change is rolled back) existing utilities like
    these will not work:
    - `selection:text-opacity-50`
    - `selection:[--tw-text-opacity:0.5]`
    
    Fixes #15000
    
    ---------
    
    Co-authored-by: Adam Wathan <[email protected]>
    thecrypticace and adamwathan authored Nov 14, 2024
    Configuration menu
    Copy the full SHA
    d093dce View commit details
    Browse the repository at this point in the history
  2. v3.4.15

    thecrypticace committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    6069a81 View commit details
    Browse the repository at this point in the history

Commits on Nov 28, 2024

  1. Fix Plugin type issue (#14668)

    This is a quick fix to an issue where the types for PluginsConfig don't
    match those used in plugins like
    [`@tailwindcss/container-queries`](https://github.com/tailwindlabs/tailwindcss-container-queries).
    
    This was caught by TypeScript with [`exactOptionalPropertyTypes`](
    https://www.typescriptlang.org/tsconfig/exactOptionalPropertyTypes.html)
    enabled, where TypeScript checks if `undefined` can be supplied as a
    value for optional types.
    
    I felt that it made more sense to fix this here, as it makes the core
    types more flexible, as opposed to each plugin needing to fix this
    when/if they hit it.
    
    ---------
    
    Co-authored-by: Philipp Spiess <[email protected]>
    mrmckeb and philipp-spiess authored Nov 28, 2024
    Configuration menu
    Copy the full SHA
    2702cfc View commit details
    Browse the repository at this point in the history

Commits on Dec 3, 2024

  1. fix: update lilconfig for ESM and Windows support (#15289)

    This PR updates `lilconfig` from v2.1.0 to v3.1.3. Significant
    improvements to this package include Windows absolute path support as
    well as ESM config files support. This supersedes
    #14029 which has fallen
    behind and has conflicts with the upstream branch. This is a critical
    update for Next.js apps running in development which have dependencies
    on packages that use an updated version of `lilconfig`. I understand
    that v4 will not be using `lilconfig` but it's an important update for
    users on v3.x in the meantime.
    
    ---------
    
    Co-authored-by: Jordan Pittman <[email protected]>
    shellscape and thecrypticace authored Dec 3, 2024
    Configuration menu
    Copy the full SHA
    8c8c986 View commit details
    Browse the repository at this point in the history
  2. v3.4.16

    thecrypticace committed Dec 3, 2024
    Configuration menu
    Copy the full SHA
    8f91c27 View commit details
    Browse the repository at this point in the history
  3. Bump macos version

    thecrypticace committed Dec 3, 2024
    Configuration menu
    Copy the full SHA
    f875ab9 View commit details
    Browse the repository at this point in the history

Commits on Dec 17, 2024

  1. Work around issue with Node 22 and Jiti (#15421)

    Fixes #15374
    
    If we always use Jiti the problem should, in theory, go away (I hope).
    It does mean that loading configs is slower than it would be if they're
    written in CJS but 🤷‍♂️
    
    Wanna get this running with the integration tests to see if anything
    breaks.
    thecrypticace authored Dec 17, 2024
    Configuration menu
    Copy the full SHA
    0a836f7 View commit details
    Browse the repository at this point in the history
  2. Update changelog

    thecrypticace committed Dec 17, 2024
    Configuration menu
    Copy the full SHA
    e268b2a View commit details
    Browse the repository at this point in the history
  3. v3.4.17

    thecrypticace committed Dec 17, 2024
    Configuration menu
    Copy the full SHA
    02faa15 View commit details
    Browse the repository at this point in the history
  4. Fix error

    thecrypticace committed Dec 17, 2024
    Configuration menu
    Copy the full SHA
    4f9f603 View commit details
    Browse the repository at this point in the history
Loading