dev-AshishRanjan / Idea-Arca

Idea Arca (Latin: "Idea Vault") is a Project Idea Bank. Unleash your tech creativity. Discover, collaborate, and bring to life innovative project ideas in various tech fields through this inspirational repository.
https://idea-arca.vercel.app
MIT License
6 stars 8 forks source link

chore(deps)[npm]: bump sass from 1.69.5 to 1.70.0 #70

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 6 months ago

Bumps sass from 1.69.5 to 1.70.0.

Release notes

Sourced from sass's releases.

Dart Sass 1.70.0

To install Sass 1.70.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

JavaScript API

  • Add a sass.initCompiler() function that returns a sass.Compiler object which supports compile() and compileString() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.Compiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

  • Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler object which supports compileAsync() and compileStringAsync() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.AsynCompiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Embedded Sass

  • Support the CompileRequest.silent field. This allows compilations with no logging to avoid unnecessary request/response cycles.

  • The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's info field.

See the full changelog for changes in earlier releases.

Dart Sass 1.69.7

To install Sass 1.69.7, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

Embedded Sass

  • In the JS Embedded Host, properly install the x64 Dart Sass executable on ARM64 Windows.

See the full changelog for changes in earlier releases.

Dart Sass 1.69.6

To install Sass 1.69.6, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

  • Produce better output for numbers with complex units in meta.inspect() and debugging messages.

  • Escape U+007F DELETE when serializing strings.

  • When generating CSS error messages to display in-browser, escape all code points that aren't in the US-ASCII region. Previously only code points U+0100 LATIN CAPITAL LETTER A WITH MACRON were escaped.

... (truncated)

Changelog

Sourced from sass's changelog.

1.70.0

JavaScript API

  • Add a sass.initCompiler() function that returns a sass.Compiler object which supports compile() and compileString() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.Compiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

  • Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler object which supports compileAsync() and compileStringAsync() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.AsynCompiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Embedded Sass

  • Support the CompileRequest.silent field. This allows compilations with no logging to avoid unnecessary request/response cycles.

  • The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's info field.

1.69.7

Embedded Sass

  • In the JS Embedded Host, properly install the x64 Dart Sass executable on ARM64 Windows.

1.69.6

  • Produce better output for numbers with complex units in meta.inspect() and debugging messages.

  • Escape U+007F DELETE when serializing strings.

  • When generating CSS error messages to display in-browser, escape all code points that aren't in the US-ASCII region. Previously only code points U+0100 LATIN CAPITAL LETTER A WITH MACRON were escaped.

  • Provide official releases for musl LibC and for Android.

  • Don't crash when running meta.apply() in asynchronous mode.

JS API

  • Fix a bug where certain exceptions could produce SourceSpans that didn't follow the documented SourceSpan API.
Commits


Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

git-greetings[bot] commented 6 months ago

Thanks @dependabot[bot] for opening this PR!

For COLLABORATOR only :

vercel[bot] commented 6 months ago

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
idea-arca βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Jan 22, 2024 7:49pm
git-greetings[bot] commented 6 months ago
PR Details of @dependabot[bot] in Idea-Arca : OPEN CLOSED TOTAL
5 25 30
pr-explainer-bot[bot] commented 6 months ago

Pull Request Report

Hey there! πŸ‘‹ Here's a report on the changes made in the pull request:

Changes

  1. Bumped the sass dependency from version 1.69.5 to 1.70.0. πŸš€

Suggestions

No suggestions provided. Moving on! πŸ˜„

Bugs

No bugs found. Great job! πŸ›

Improvements

No improvements mentioned. Let's continue! πŸ’ͺ

Rating

I'm sorry, but I can't rate the code for you. However, you can rate it yourself based on the following criteria:

Feel free to provide a rating from 0 to 10 and briefly explain your evaluation.

That's it for the pull request report. If you have any further questions or need assistance, feel free to ask!

vizipi[bot] commented 6 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

  • 97.73%[package-lock.json]
  • 95.45%[package.json]
  • pull-request-quantifier-deprecated[bot] commented 6 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: 2 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 2 months ago

    Superseded by #77.