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.

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

Update dependency @astrojs/tailwind to v5 #173

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 3, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

withastro/astro (@​astrojs/tailwind)

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

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies label Sep 3, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Sep 3, 2023

⚠ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @example/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/astro
npm ERR!   astro@"^2.8.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer astro@"^3.0.0" from @astrojs/[email protected]
npm ERR! node_modules/@astrojs/tailwind
npm ERR!   @astrojs/tailwind@"^5.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/f795c0/a37ee9/cache/others/npm/_logs/2023-09-03T16_38_57_585Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f795c0/a37ee9/cache/others/npm/_logs/2023-09-03T16_38_57_585Z-debug-0.log

@jacopen jacopen closed this Sep 3, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Sep 3, 2023

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/astrojs-tailwind-5.x branch September 3, 2023 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant