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

fix(deps): update dependency @astrojs/tailwind to v6 #55

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency @astrojs/tailwind to v6 #55

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/tailwind (source) ^3.1.3 -> ^6.0.0 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/tailwind)

v6.0.0

Compare Source

Major Changes

  • #​13049 2ed4bd9 Thanks @​florian-lefebvre! - Deprecates the integration

    Tailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall @astrojs/tailwind and follow the Tailwind documentation for manual installation.

    This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.

v5.1.5

Compare Source

Patch Changes

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes
Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.0

Compare Source

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from 1c63944 to af12a33 Compare December 3, 2024 12:00
@renovate renovate bot changed the title fix(deps): update astro monorepo (major) fix(deps): update astro monorepo to v5 (major) Dec 3, 2024
@renovate renovate bot changed the title fix(deps): update astro monorepo to v5 (major) fix(deps): update dependency @astrojs/tailwind to v5 Dec 18, 2024
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from af12a33 to b57e9ed Compare January 30, 2025 15:16
@renovate renovate bot changed the title fix(deps): update dependency @astrojs/tailwind to v5 fix(deps): update dependency @astrojs/tailwind to v6 Jan 30, 2025
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: apps/movie-quotes-frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: movie-quotes-frontend@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/astro
npm ERR!   dev astro@"^2.5.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer astro@"^3.0.0 || ^4.0.0 || ^5.0.0" from @astrojs/[email protected]
npm ERR! node_modules/@astrojs/tailwind
npm ERR!   @astrojs/tailwind@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-30T15_16_34_032Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants