thomasKn / astro-shopify

A lightweight and powerful ecommerce starter theme to build headless Shopify storefronts with Astro.
https://astro-shopify.frontvibe.com
MIT License
332 stars 99 forks source link

Bump the patch-minor group across 1 directory with 6 updates #76

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the patch-minor group with 6 updates in the / directory:

Package From To
@nanostores/persistent 0.10.1 0.10.2
@shopify/hydrogen-react 2024.7.1 2024.7.2
astro 4.12.2 4.13.3
nanostores 0.10.3 0.11.2
prettier-plugin-tailwindcss 0.6.5 0.6.6
tailwindcss 3.4.7 3.4.9

Updates @nanostores/persistent from 0.10.1 to 0.10.2

Release notes

Sourced from @​nanostores/persistent's releases.

0.10.2

  • Added Nano Stores 0.11 support.
Changelog

Sourced from @​nanostores/persistent's changelog.

0.10.2

  • Added Nano Stores 0.11 support.
Commits


Updates @shopify/hydrogen-react from 2024.7.1 to 2024.7.2

Release notes

Sourced from @​shopify/hydrogen-react's releases.

@​shopify/hydrogen-react@​2024.7.2

Patch Changes

  • Improve performance of currency formatting (#2372) by @​blittle

  • Prevent sending analytics data to Shopify when Chrome-Lighthouse user agent is detected (#2401) by @​wizardlyhel

Changelog

Sourced from @​shopify/hydrogen-react's changelog.

2024.7.2

Patch Changes

  • Improve performance of currency formatting (#2372) by @​blittle

  • Prevent sending analytics data to Shopify when Chrome-Lighthouse user agent is detected (#2401) by @​wizardlyhel

Commits
  • 37ec3bd [ci] release 2024-07 (#2378)
  • b09e9a4 Prevent sending analytics to Shopify when Chrome-Lighthouse user agent is d...
  • cfbfc82 Improve performance of currency formatting by caching underlying Intl.NumberF...
  • 25ab903 Fix the docs (#2355)
  • See full diff in compare view


Updates astro from 4.12.2 to 4.13.3

Release notes

Sourced from astro's releases.

astro@4.13.3

Patch Changes

  • #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

  • #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

  • #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

    • Removes "Confirm post resubmission?" dialog when refreshing a result.
    • Removes the ?_astroAction=NAME flag when a result is rendered.

    Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

    For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

    <form method="POST" action={'/success' + actions.signup}></form>
    
    • On success, Astro will redirect to /success.
    • On error, Astro will redirect back to the current page.

    You can retrieve the action result from either page using the Astro.getActionResult() function.

    Note on security

    This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

    The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

astro@4.13.2

Patch Changes

  • #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

  • #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

  • #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

    Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

  • #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

  • #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

  • #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

astro@4.13.1

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.3

Patch Changes

  • #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

  • #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

  • #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

    • Removes "Confirm post resubmission?" dialog when refreshing a result.
    • Removes the ?_astroAction=NAME flag when a result is rendered.

    Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

    For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

    <form method="POST" action={'/success' + actions.signup}></form>
    
    • On success, Astro will redirect to /success.
    • On error, Astro will redirect back to the current page.

    You can retrieve the action result from either page using the Astro.getActionResult() function.

    Note on security

    This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

    The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

4.13.2

Patch Changes

  • #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

  • #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

  • #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

    Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

  • #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

  • #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

  • #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

... (truncated)

Commits


Updates nanostores from 0.10.3 to 0.11.2

Release notes

Sourced from nanostores's releases.

0.11.2

0.11.1

  • Fixed types.

0.11.0

Changelog

Sourced from nanostores's changelog.

0.11.2

0.11.1

  • Fixed types.

0.11.0

Commits


Updates prettier-plugin-tailwindcss from 0.6.5 to 0.6.6

Release notes

Sourced from prettier-plugin-tailwindcss's releases.

v0.6.6

  • Add support for prettier-plugin-multiline-arrays (#299)
  • Add resolution cache for known plugins (#301)
  • Support Tailwind CSS v4.0.0-alpha.19 (#310)
Changelog

Sourced from prettier-plugin-tailwindcss's changelog.

[0.6.6] - 2024-08-09

  • Add support for prettier-plugin-multiline-arrays (#299)
  • Add resolution cache for known plugins (#301)
  • Support Tailwind CSS v4.0.0-alpha.19 (#310)
Commits


Updates tailwindcss from 3.4.7 to 3.4.9

Release notes

Sourced from tailwindcss's releases.

v3.4.9

Fixed

  • No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Fixed

  • Fix minification when using nested CSS (#14105)
  • Warn when broad glob patterns are used in the content configuration (#14140)
Changelog

Sourced from tailwindcss's changelog.

[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)
Commits


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
vercel[bot] commented 2 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
astro-shopify ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 12, 2024 9:44am