Skip to content

Latest commit

History

History
413 lines (235 loc) · 41.8 KB

CHANGELOG.md

File metadata and controls

413 lines (235 loc) · 41.8 KB

@astrojs/tailwind

5.1.2

Patch Changes

  • #121618e500f2Thanks@delucis!- Adds keywords topackage.jsonto improve categorization in the Astro integrations catalog

5.1.1

Patch Changes

5.1.0

Minor Changes

Patch Changes

5.0.4

Patch Changes

5.0.3

Patch Changes

  • #93132f110a501Thanks@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

  • #8188d0679a666Thanks@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.

  • #81796011d52d3Thanks@matthewp!- Astro 3.0 Release Candidate

Patch Changes

5.0.0-rc.1

Major Changes

Patch Changes

5.0.0-beta.0

Major Changes

  • 1eae2e3f7Thanks@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

  • #7391556fd694aThanks@bluwy!- Rename optionsconfig.pathtoconfigFile,andconfig.applyBaseStylestoapplyBaseStyles.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,
    }),
    ],
    });
  • #67243f1cb6b1aThanks@TomPichaud!- Let thetailwindcssPostCSS plugin load its config file itself. This changes the Tailwind config loading behaviour where it is loaded fromprocess.cwd()instead of the projectroot.

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

    // astro.config.mjs
    import{defineConfig}from'astro/config';
    importtailwindfrom'@astrojs/tailwind';
    import{fileURLToPath}from'url';
    
    exportdefaultdefineConfig({
    integrations:[
    tailwind({
    configFile:fileURLToPath(newURL('./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 duringastro add tailwind,but if it does not exist, you can manually create atailwind.config.cjsfile 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

  • #5717a3a7fc929Thanks@bluwy!- Removestyle.postcssAstro config. Refactor Tailwind integration to configure throughviteinstead. Also disablesautoprefixerin dev.

  • #58067572f7402Thanks@matthewp!- Make astro apeerDependencyof integrations

    This marksastroas apeerDependencyof several packages that are already gettingmajorversion 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

  • #58067572f7402Thanks@matthewp!- Make astro apeerDependencyof integrations

    This marksastroas apeerDependencyof several packages that are already gettingmajorversion 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

  • #5717a3a7fc929Thanks@bluwy!- Removestyle.postcssAstro config. Refactor Tailwind integration to configure throughviteinstead. Also disablesautoprefixerin dev.

2.1.3

Patch Changes

2.1.2

Patch Changes

2.1.1

Patch Changes

2.1.0

Minor Changes

  • #4947a5e3ecc80Thanks@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 yourtsconfig.jsonortailwind.config.jsconfigs, the changes will reload automatically without the need to restart your dev server.

2.0.2

Patch Changes

  • #4842812658ad2Thanks@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

  • #3099254a8f37Thanks@tony-sull!- Removes theapplyAstroPresetintegration option. Tailwind presets can be disabled directly from the Tailwind config file by includingpresets: []

    See theTailwind preset docsfor more details.

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

Patch Changes

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

0.0.2

Patch Changes

  • #28315315c3f7Thanks@bholmesdev!- Add support for tailwind config files. These can either be a standardtailwind.config.js|cjs|mjs,or a custom filename as specified in your integration config.
  • #28473b621f7aThanks@tony-sull!- Adds keywords to the official integrations to support discoverability on Astro's Integrations site

0.0.2-next.0

Patch Changes

  • #28315315c3f7Thanks@bholmesdev!- Add support for tailwind config files. These can either be a standardtailwind.config.js|cjs|mjs,or a custom filename as specified in your integration config.
  • #28473b621f7aThanks@tony-sull!- Adds keywords to the official integrations to support discoverability on Astro's Integrations site