Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use local user css cache for apply #7524

Merged
merged 13 commits into from Feb 25, 2022
Merged

Use local user css cache for apply #7524

merged 13 commits into from Feb 25, 2022

Commits on Feb 24, 2022

  1. Fix context reuse test

    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    3dd521e View commit details
    Browse the repository at this point in the history

  2. Don't update files with at-apply when content changes

    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    d442ac5 View commit details
    Browse the repository at this point in the history

  3. Prevent at-apply directives from creating new contexts

    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    326bf53 View commit details
    Browse the repository at this point in the history

  4. Rework apply to use local postcss root 

    We were storing user CSS in the context so we could use it with apply. The problem is that this CSS does not get updated on save unless it has a tailwind directive in it resulting in stale apply caches. This could result in either stale generation or errors about missing classes.
    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    8fccb99 View commit details
    Browse the repository at this point in the history

  5. Don’t build local cache unless @apply is used

    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    a24e794 View commit details
    Browse the repository at this point in the history

  6. Speed up structural cloning 

    The previous method was very inefficient as PostCSS was recursively cloning the entire tree. We only care about cloning the node itself as we’re replacing its children. This is about 4x faster on large CSS blobs.
    @thecrypticace
    thecrypticace committed Feb 24, 2022
    Copy the full SHA
    89c4f68 View commit details
    Browse the repository at this point in the history

Commits on Feb 25, 2022

  1. Simplify

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    f5e37c6 View commit details
    Browse the repository at this point in the history

  2. Change to let

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    5302fc6 View commit details
    Browse the repository at this point in the history

  3. Update test name

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    490e8bc View commit details
    Browse the repository at this point in the history

  4. Change which offset is user

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    a602a79 View commit details
    Browse the repository at this point in the history

  5. Add comments

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    0b450fa View commit details
    Browse the repository at this point in the history

  6. Update changelog

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    c78aa7b View commit details
    Browse the repository at this point in the history

  7. Fix test name

    @thecrypticace
    thecrypticace committed Feb 25, 2022
    Copy the full SHA
    29bc320 View commit details
    Browse the repository at this point in the history