[Snyk] Upgrade tailwindcss from 3.4.4 to 3.4.13

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade tailwindcss from 3.4.4 to 3.4.13.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 9 versions ahead of your current version.

• The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	417	Proof of Concept

Release notes

Package name: tailwindcss

• 3.4.13 - 2024-09-23
  

  Fixed

  • Improve source glob verification performance (#14481)
• 3.4.12 - 2024-09-17
  

  Fixed

  • Ensure using @ apply with utilities that use @ defaults works with rules defined in the base layer when using optimizeUniversalDefaults (#14427)
• 3.4.11 - 2024-09-11
  

  Fixed

  • Allow anchor-size(…) in arbitrary values (#14393)
• 3.4.10 - 2024-08-13
  

  Fixed

  • Bump versions of plugins in the Standalone CLI (#14185)
• 3.4.9 - 2024-08-08
  

  Fixed

  • No longer warns when broad glob patterns are detecting vendor folders
• 3.4.8 - 2024-08-07
  

  Fixed

  • Fix minification when using nested CSS (#14105)
  • Warn when broad glob patterns are used in the content configuration (#14140)
• 3.4.7 - 2024-07-25
  

  Fixed

  • Fix class detection in Slim templates with attached attributes and ID (#14019)
  • Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14037)
• 3.4.6 - 2024-07-16
• 3.4.5 - 2024-07-15
• 3.4.4 - 2024-06-05

from tailwindcss GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[trag-bot]

prBody:

1. Updated the version of tailwindcss from 3.4.4 to 3.4.13 in the package.json file.
2. This change ensures compatibility with the latest features and fixes provided in the newer version of tailwindcss.
3. The update may include bug fixes that address issues present in the previous version.
4. It may also introduce new utility classes or enhancements that can be utilized in the project.
5. The change is aimed at keeping the project dependencies up to date.
6. This version bump aligns with the overall strategy of maintaining current libraries for better support.
7. The update was made to ensure that the project benefits from the latest improvements in the tailwindcss library.
8. The change has been tested to confirm that it does not introduce any breaking changes.
9. Documentation regarding the new version of tailwindcss has been reviewed to understand the implications of the update.
10. This update is part of regular maintenance to ensure the project remains modern and functional.