Infrastructure/astro
0
Fork 0
mirror of https://github.com/withastro/astro.git synced 2024-12-16 21:46:22 -05:00
Code Issues Activity
astro/packages/integrations/tailwind/CHANGELOG.md
Houston (Bot) 97342d218e
[ci] release (#9457) 
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2023-12-20 17:39:13 +00:00

41 KiB
Raw Blame History

@astrojs/tailwind

5.0.4

Patch Changes

5.0.3

Patch Changes

  • #9313 2f110a501 Thanks @matthewp! - Upgrade for compatibility with Astro 4

    The Tailwind now supports both Astro 3 and Astro 4.

6.0.0-beta.0

Patch Changes

5.0.2

Patch Changes

5.0.1

Patch Changes

5.0.0

Major Changes

  • #8188 d0679a666 Thanks @ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

  • #8179 6011d52d3 Thanks @matthewp! - Astro 3.0 Release Candidate

Patch Changes

5.0.0-rc.1

Major Changes

Patch Changes

5.0.0-beta.0

Major Changes

  • 1eae2e3f7 Thanks @Princesseuh! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

Patch Changes

4.0.0

Major Changes

  • #7391 556fd694a Thanks @bluwy! - Rename options config.path to configFile, and config.applyBaseStyles to applyBaseStyles. If you are using these options, you need to migrate to the new names.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import tailwind from '@astrojs/tailwind';

export default defineConfig({
  integrations: [
    tailwind({
-      config: {
-        path: '...',
-        applyBaseStyles: true,
-      },
+      configFile: '...',
+      applyBaseStyles: true,
    }),
  ],
});

  • #6724 3f1cb6b1a Thanks @TomPichaud! - Let the tailwindcss PostCSS plugin load its config file itself. This changes the Tailwind config loading behaviour where it is loaded from process.cwd() instead of the project root.

    If your Tailwind config file is not located in the current working directory, you will need to configure the integration's configFile option to load from a specific path:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import tailwind from '@astrojs/tailwind';
import { fileURLToPath } from 'url';

export default defineConfig({
  integrations: [
    tailwind({
      configFile: fileURLToPath(new URL('./tailwind.config.cjs', import.meta.url)),
    }),
  ],
});

    This change also requires a Tailwind config file to exist in your project as a fallback config is no longer provided. It is set up automatically during astro add tailwind, but if it does not exist, you can manually create a tailwind.config.cjs file in your project root:

    // tailwind.config.cjs
/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
  theme: {
    extend: {},
  },
  plugins: [],
};

Patch Changes

3.1.3

Patch Changes

3.1.2

Patch Changes

3.1.1

Patch Changes

3.1.0

Minor Changes

Patch Changes

3.0.1

Patch Changes

3.0.0

Major Changes

  • #5717 a3a7fc929 Thanks @bluwy! - Remove style.postcss Astro config. Refactor Tailwind integration to configure through vite instead. Also disables autoprefixer in dev.

  • #5806 7572f7402 Thanks @matthewp! - Make astro a peerDependency of integrations

    This marks astro as a peerDependency of several packages that are already getting major version bumps. This is so we can more properly track the dependency between them and what version of Astro they are being used with.

Patch Changes

3.0.0-beta.2

See changes in 3.0.0-beta.2

Patch Changes

3.0.0-beta.1

See changes in 3.0.0-beta.1

Major Changes

  • #5806 7572f7402 Thanks @matthewp! - Make astro a peerDependency of integrations

    This marks astro as a peerDependency of several packages that are already getting major version bumps. This is so we can more properly track the dependency between them and what version of Astro they are being used with.

Patch Changes

3.0.0-beta.0

See changes in 3.0.0-beta.0

Major Changes

  • #5717 a3a7fc929 Thanks @bluwy! - Remove style.postcss Astro config. Refactor Tailwind integration to configure through vite instead. Also disables autoprefixer in dev.

2.1.3

Patch Changes

2.1.2

Patch Changes

2.1.1

Patch Changes

2.1.0

Minor Changes

  • #4947 a5e3ecc80 Thanks @JuanM04! - ## HMR on config file changes

    New in this release is the ability for config changes to automatically reflect via HMR. Now when you edit your tsconfig.json or tailwind.config.js configs, the changes will reload automatically without the need to restart your dev server.

2.0.2

Patch Changes

  • #4842 812658ad2 Thanks @bluwy! - Add missing dependencies, support strict dependency installation (e.g. pnpm)

2.0.1

Patch Changes

2.0.0

Migration to v2

Tailwind CSS is now a peer dependency, so you will need to install it manually when updating this integration:

npm install tailwindcss

Major Changes

1.0.1

Patch Changes

1.0.0

Major Changes

0.2.5

Patch Changes

0.2.4

Patch Changes

0.2.3

Patch Changes

0.2.2

Patch Changes

0.2.1

Patch Changes

0.2.0

Minor Changes

  • #3099 254a8f37 Thanks @tony-sull! - Removes the applyAstroPreset integration option. Tailwind presets can be disabled directly from the Tailwind config file by including presets: []

    See the Tailwind preset docs for more details.

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

Patch Changes

  • e425f896 Thanks @FredKSchott! - Adds an option to opt-out of the default base styles for the Tailwind integration

0.0.2

Patch Changes

  • #2831 5315c3f7 Thanks @bholmesdev! - Add support for tailwind config files. These can either be a standard tailwind.config.js|cjs|mjs, or a custom filename as specified in your integration config.
  • #2847 3b621f7a Thanks @tony-sull! - Adds keywords to the official integrations to support discoverability on Astro's Integrations site

0.0.2-next.0

Patch Changes

  • #2831 5315c3f7 Thanks @bholmesdev! - Add support for tailwind config files. These can either be a standard tailwind.config.js|cjs|mjs, or a custom filename as specified in your integration config.
  • #2847 3b621f7a Thanks @tony-sull! - Adds keywords to the official integrations to support discoverability on Astro's Integrations site