Bump @astrojs/tailwind from 3.1.3 to 4.0.0 in /astro

[dependabot]

Bumps @astrojs/tailwind from 3.1.3 to 4.0.0.

Release notes

Sourced from @​astrojs/tailwind's releases.

@​astrojs/tailwind@​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}'],

... (truncated)

Changelog

Sourced from @​astrojs/tailwind's changelog.

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 = {

... (truncated)

Commits

• f87680f [ci] release (#7390)
• 556fd69 Rename tailwind integration options (#7391)
• 3f1cb6b @​astrojs/tailwind: simplify, upgrade & fix support for ts config file (#6724)
• 06315a1 [ci] release (#7368)
• 4f70912 [ci] release (#7354)
• e138f66 [ci] release (#7318)
• 8a029d9 [ci] release (#7312)
• d5a0898 [ci] release (#7295)
• c64dfdd [ci] release (#7254)
• ba865f5 [ci] release (#7190)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)