chore(deps)[npm]: bump astro from 2.10.15 to 3.4.0

dependabot[bot] commented 11 months ago

Bumps astro from 2.10.15 to 3.4.0.

Release notes

astro@3.4.0

Minor Changes
#8755 fe4079f05 Thanks @matthewp! - Page Partials

A page component can now be identified as a partial page, which will render its HTML content without including a <! DOCTYPE html> declaration nor any <head> content.

A rendering library, like htmx or Stimulus or even just jQuery can access partial content on the client to dynamically update only parts of a page.

Pages marked as partials do not have a doctype or any head content included in the rendered result. You can mark any page as a partial by setting this option:
---
export const partial = true;
---
<li>This is a single list item.</li>
Other valid page files that can export a value (e.g. .mdx) can also be marked as partials.

Read more about Astro page partials in our documentation.
#8821 4740d761a Thanks @Princesseuh! - Improved image optimization performance

Astro will now generate optimized images concurrently at build time, which can significantly speed up build times for sites with many images. Additionally, Astro will now reuse the same buffer for all variants of an image. This should improve performance for websites with many variants of the same image, especially when using remote images.

No code changes are required to take advantage of these improvements.
#8757 e99586787 Thanks @Princesseuh! - Dev Overlay (experimental)

Provides a new dev overlay for your browser preview that allows you to inspect your page islands, see helpful audits on performance and accessibility, and more. A Dev Overlay Plugin API is also included to allow you to add new features and third-party integrations to it.

You can enable access to the dev overlay and its API by adding the following flag to your Astro config:
// astro.config.mjs
export default {
  experimental: {
    devOverlay: true,
  },
};
Read the Dev Overlay Plugin API documentation for information about building your own plugins to integrate with Astro's dev overlay.
#8880 8c3d4a859 Thanks @alexanderniebuhr! - Moves the logic for overriding the image service out of core and into adapters. Also fixes a regression where a valid astro:assets image service configuration could be overridden.
astro@3.3.4

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

3.4.0

Minor Changes
#8755 fe4079f05 Thanks @matthewp! - Page Partials

A page component can now be identified as a partial page, which will render its HTML content without including a <! DOCTYPE html> declaration nor any <head> content.

A rendering library, like htmx or Stimulus or even just jQuery can access partial content on the client to dynamically update only parts of a page.

Pages marked as partials do not have a doctype or any head content included in the rendered result. You can mark any page as a partial by setting this option:
---
export const partial = true;
---
<li>This is a single list item.</li>
Other valid page files that can export a value (e.g. .mdx) can also be marked as partials.

Read more about Astro page partials in our documentation.
#8821 4740d761a Thanks @Princesseuh! - Improved image optimization performance

Astro will now generate optimized images concurrently at build time, which can significantly speed up build times for sites with many images. Additionally, Astro will now reuse the same buffer for all variants of an image. This should improve performance for websites with many variants of the same image, especially when using remote images.

No code changes are required to take advantage of these improvements.
#8757 e99586787 Thanks @Princesseuh! - Dev Overlay (experimental)

Provides a new dev overlay for your browser preview that allows you to inspect your page islands, see helpful audits on performance and accessibility, and more. A Dev Overlay Plugin API is also included to allow you to add new features and third-party integrations to it.

You can enable access to the dev overlay and its API by adding the following flag to your Astro config:
// astro.config.mjs
export default {
  experimental: {
    devOverlay: true,
  },
};
Read the Dev Overlay Plugin API documentation for information about building your own plugins to integrate with Astro's dev overlay.
#8880 8c3d4a859 Thanks @alexanderniebuhr! - Moves the logic for overriding the image service out of core and into adapters. Also fixes a regression where a valid astro:assets image service configuration could be overridden.
3.3.4

... (truncated)

Commits

7a35aed [ci] release (#8917)
fe4079f Partials (#8755)
ec7f531 Fix examples smoke test fail (#8923)
8c3d4a8 fix noop overwrite image service regression (#8880)
e995867 feat: Add a dev overlay (#8757)
4740d76 feat: Rework image generation to improve performance (#8821)
a86b41c [ci] release (#8895)
dbff442 Chores: Tidying up the view transition router (#8889)
26b77b8 Fix CSS modules ordering (#8877)
42a83ff [ci] release (#8861)
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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

vercel[bot] commented 11 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
idea-arca	❌ Failed (Inspect)			Oct 31, 2023 4:28pm

sweep-ai[bot] commented 11 months ago

Apply Sweep Rules to your PR?

[ ] Apply: Leftover TODOs in the code should be handled.
[ ] Apply: All new business logic should have corresponding unit tests in the tests/ directory.
[ ] Apply: Any clearly inefficient or repeated code should be optimized or refactored.

vizipi[bot] commented 11 months ago

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below ) Feedback always welcome

No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments.

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

Committed file ranks

(click to expand)

95.45%[package.json]

97.73%[package-lock.json]

pull-request-quantifier-deprecated[bot] commented 11 months ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

dependabot[bot] commented 11 months ago

Superseded by #49.

dev-AshishRanjan / Idea-Arca