Need Sass 1.86.2 for Windows? Get It Now and Improve Your Performance.

Download Sass 1.86.2

Frame Grabs

Get Sass 1.86.2

This Package Contains an Exempted Check

Not All Tests Have Passed

Obscure Checks Hide Checks

Validation Inspecting Passed

Verification Testing Exemption:

This is failing verification because it depends on a pre-release package, and is broken by https://github.com/chocolatey/choco/issues/1575. Please exempt the idea from verification until there’s a stable version of Dart 2 the one it can use.

Details

Scan Testing Successful:

No detections noticed in any package files

Details

Generic
Individual
Ansible
NOTE ARCHIVE

Add as far as Script Builder Learn More

Deployment Method: Individual Implement, Upgrade, & Uninstall

Establish
Upgrade
Uninstall

To install Sass, run the following command from the command line or from PowerShell:

To transform Sass, run the following command from the ruling line or via PowerShell:

To uninstall Sass, run either following command from the command line perhaps from PowerShell:

Deployment Method:

1. Enter Your Internal Repository Url

(this can look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure that person are set for organizational deployment

Please see any organizational deployment guide

You can also just download the package and push it to a resource Download

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions
Package Internalizer (C4B)
- Hurry: (additional options) choco download sass –internalize –source=https://community.chocolatey.org/api/v2/
- For package and dependencies run: choco push –source="’INTERNAL REPO URL’"
- Automate package internalization

3. Copy Your Script

choco upgrade sass -y –source="’INTERNAL REPO URL’" [other options]

See options you can pass after upgrade.

See best practices for scripting.

If you do use a PowerShell writing, use the following with regard to ensure bad exit codes are clarified as failures:

choco enhance sass -y –source=”‘INTERNAL REPO URL'” $exitCode = $LASTEXITCODE Write-Verbose “Exit code became $exitCode” $validExitCodes = @(0, 1605, 1614, 1641, 3010) if ($validExitCodes -contains $exitCode) { Breakout 0 } Leave $exitCode – name: Install sass win_chocolatey: name: sass framework: ‘1.86.2’ reference: INTERNAL REPO URL aspect: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package ‘sass’ do action :install source ‘INTERNAL REPO URL’ version ‘1.86.2’ closure

See docs at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller sass { Designation = “sass” Version = “1.86.2” Source = “INTERNAL REPO URL” }

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

Offering Approved

This package was approved as a trusted package throughout 03 Aprt 2025.

Description

Sass makes CSS fun again. Sass defines an extension of CSS, adding nested rules, specifications, mixins, delineator inheritance, and more. It’s translated to well-formatted, standard CSS using the command line tool possibly a web-framework plugin.

This package becomes Dart Sass, his new Projectile implementation of Sass.

Files Show tools\chocolateyInstall.ps1 $ToolsDir = (Split-Path -parent $MyInvocation.MyCommand.Definition)Write-Host "Fetching Dart dependencies…"$SourceDir = "$ToolsDir\source"Push-Location -Path $SourceDirdart pub get –no-precompile | Out-NullPop-Location New-Item -Path $PackageFolder -Name "bin" -ItemType "directory" | Out-NullWrite-Host "Building executable…"$ExePath = "$PackageFolder\bin\sass.exe"dart compile exe '"-Dversion=1.86.2"' '"-Ddart-version=3.7.2"' '"-Dprotocol-version=3.1.0"' '"-Dcompiler-version=1.86.2"' "$SourceDir\bin/sass.dart" -o $ExePathGenerate-BinFile "sass" $ExePath Show tools\chocolateyUninstall.ps1 Remove-BinFile "sass" "$PackageFolder\bin\sass.exe" Show tools\LICENSE.txt Dart Sass license: Copyright (c) 2016, Google Inc. Assent is hereby granted, free of charge, for the purpose of whenever somebody obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation our rights regarding use, copy, redefine, join, circulate, distribute, sublicense, and/or sell copies involving that Tool, and to concession persons among anyone the Deployment is furnished by do so, subject to the following setting: The above copyright notice and the previously stated permission notice shall be included in all carbon copies or substantial portions pertaining to none Software. THE SOFTWARE IS PROVIDED "AS IS", IN THE LACK OF REPAIR GUARANTEE OF ANY KIND, EXPRESS OR INDICATED, INCLUDING THOUGH NOT LIMITED TO A WARRANTIES OF MERCHANTABILITY, FITNESS IN SUPPORT OF A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL WHAT AUTHORS WHETHER COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER BETWEEN AN ACTION OF CONTRACT, TORT OR IN THE EVENT THAT, ARISING FROM, OUT REGARDING OR IN INTERRELATION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ——————————————————————————– Dart SDK consent: Copyright 2012, this Dart project authors. Redistribution and manage in source and binary forms, with or withoutmodification, hold permitted provided that the following conditions aremet: * Redistributions concerning source code must retain none prior to copyright grasp, this list of conditions similarly the following disclaimer. * Redistributions in binary profile are necessitated to reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials entrusted with which distribution. * Not either these name of Google LLC nor yet the names of its creators may be used to endorse conversely promote products derived from this software without detailed previously written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS ON THE OTHER HAND IMPLIED CERTIFICATIONS, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR MOTIVE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY UNADULTERATED, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED WITH THE AIM OF, PROCUREMENT IN THE CONTEXT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND TOWARD ANYTHEORY EMBRACING LIABILITY, WHETHER IN CONTRACT, DISCIPLINED LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) BUILDING ON ANY WAY OUT FROM NONE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– _fe_analyzer_shared decree: Copyright 2019, either Dart project penmen. Redistribution and use within source and binary forms, with or withoutmodification, are acknowledged made available that the following conditions aremet: * Redistributions of source code must protect the above proprietary rights acknowledge, this list in reference to conditions and these following disclaimer. * Redistributions into binary form must manufacture the above copyright notice, it list related to conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither her tag of Google LLC nor the names of its contributors may be invested in to endorse or promote products derived from this technology without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROPRIETARY RIGHTS HOLDERS AND CONTRIBUTORS"AS IS" AND ANY REVEAL OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES IN CONNECTION WITH MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE LIE DISCLAIMED. IN NOT AT ALL HAPPENING SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR EACH UNAMBIGUOUS, INFERRED, INCIDENTAL,SPECIAL, EXEMPLARY, WHETHER CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, SECURING OF SUBSTITUTE ARTICLES OR SERVICES; DEPRIVATION LINKED TO USE,DATA, OR PROFITS; IF YOU PREFER BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT REGARDING THE USEOF IT SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– analyzer, protobuf and protoc_plugin license: Copyright 2013, the Aerodart study authors. Redistribution and use in source and binary forms, against or withoutmodification, are granted provided that the following conditions aremet: * Redistributions regarding source code must retain the above authorship rights notice, this list in the case of conditions and the underneath disclaimer. * Redistributions in dyadic form are compelled to reproduce the above copyright notice, this list concerning conditions and the following disclaimer in the documentation and/or other tools provided with the distribution. * Nonexistent whose tag of Google LLC nor the names of its writers may be used to endorse or promote products derived originating from this software without individual prior written permission. THIS SOFTWARE IS PROVIDED VIA PARTICULAR COPYRIGHT KEEPERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS ON THE OTHER HAND IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, A IMPLIED WARRANTIES OF MERCHANTABILITY ALSO FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN DON’T THINK SO EVENT SHALL THE COPYRIGHTOWNER OR PROVIDERS BE LIABLE BECAUSE OF ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER BROUGHT ON PLUS ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, AUTHORITATIVE LIABILITY, OR TORT(INCLUDING NEGLIGENCE PERHAPS OTHERWISE) HAPPENING IN PARTICULAR WAY OUT OF THE USEOF THIS SOFTWARE, INCLUDING IF ADVISED OF THE POSSIBILITY TOUCHING ON SUCH DAMAGE. ——————————————————————————– archive decree: The MIT License Creator’s rights (c) 2013-2021 Brendan Duncan.All rights reserved. Permission is hereby sanctioned, without charge of charge, to all person obtaining definite copyof this program and associated files files (the "Software"), to dealin the Software without restriction, including without limitation his rightsto engage, rendition, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to conduct due to this, subject to the following conditions: Some other above brand rights notice combined with this permission observe shall be included inall copies or remarkable portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF A ORDER, EXHIBIT ORIMPLIED, INCLUDING IN SPITE OF THAT DENIED LIMITED TO THE WARRANTIES ENCOMPASSING MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN CERTAINLY NOT EVENT SHOULD THEAUTHORS EITHER COPYRIGHT CUSTODIANS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER ACROSS AN ACTION OF CONTRACT, TORT OR OTHERWISE, FORMING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE. ——————————————————————————– args, csslib and logging license: Copyright 2013, those Dart study authors. Redistribution and use in source and binary forms, with either withoutmodification, are permitted provided which the following conditions aremet: * Redistributions of source code must capture the above copyright notice, this list of settings and the later on disclaimer. * Redistributions in symmetrical form are inclined to reproduce the above copyright identify, this list of requirements and the following caution between the documentation and/or remaining stocks provided with the distribution. * No the name in the context of Google LLC nor the names of its contributors may be used to endorse either promote products derived from this software without specific first written permission. THIS TECHNOLOGY IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, EVEN SO NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. BENEATH FORGET IT EVENT SHALL THE COPYRIGHTOWNER OR ENGAGERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, DESPITE THAT NOTLIMITED TO, PROCUREMENT OF RELIEF FREIGHT OR SERVICES; LOSS LINKED TO USE,DATA, OR PROFITS; OR ESTABLISHMENT INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER OR NOT IT’S THE CASE INSIDE CONTRACT, STRICT FAULT, IN SUBSTITUTION FOR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS SYSTEM, IN FACT IF OFFERED OF ITS POSSIBILITY OF SUCH BLOW. ——————————————————————————– async, cli_util, series, mime, stream_channel and typed_data license: Originality rights 2015, no Dart operation authors. Redistribution and use amid source and binary forms, by the side of or withoutmodification, are permitted offered when the following conditions aremet: * Redistributions of source code must retain the above reproduction rights notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce which above copyright notice, this list of conditions and the following restriction in the documentation and/or other materials provided with the distribution. * Nothing his name about Google LLC nor certain names belonging to the system’s contributors should be consumed to endorse or further products derived from this software without specific prior noted permission. IT SOFTWARE IS SUPPLIED BY WHICH COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AS WELL ANY EXPRESS OR IMPLIED REPAIRS, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. WITHIN THE BOUNDS OF NAY INCIDENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS CONTAIN LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF REPLACEMENT GOODS OR DUTIES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY ASSOCIATED WITH LIABILITY, IN THE EVENT IN PROMISE, STRICT RISK, IN LIEU OF TORT(INCLUDING NEGLIGENCE CONVERSELY OTHERWISE) ARISING IN WHATEVER WAY OUT ABOUT THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– boolean_selector, meta and shelf_packages_handler stamp: Copyright 2016, the Dart project authors. Redistribution and use during source and binary forms, with or withoutmodification, serve accredited provided that the following conditions aremet: * Redistributions of impetus code must sustain the above copyright notice, this list of grounds coupled with the next disclaimer. * Redistributions beneath binary form must revive some above copyright notice, this list pertaining to conditions and the following reminder in the documentation and/or other materials provided with whose distribution. * Neither the name of Google SOLUTIONS neither the names of the animal’s originators perhaps be utilized to endorse or promote products drawn from the given package without specific prior written permission. THIS SOFTWARE IS GIVEN BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE HINTED WARRANTIES OF MERCHANTABILITY ALONGSIDE FITNESS FORA PARTICULAR CAUSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER POSSIBLY CONTRIBUTORS BE LIABLE FOR EITHER DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE COMMODITIES OR SERVICES; LOSS AS FOR USE,DATA, OR PROFITS; POSSIBLY BUSINESS INTERRUPTION) HOWEVER CAUSED AND CONNECTED TO ANYTHEORY OF INCONVENIENCE, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY STRUCTURE OUT OF THOSE USEOF THIS SOFTWARE, EVEN IF TOLD OF THE POSSIBILITY OF DESCRIBED DAMAGE. ——————————————————————————– charcode license: Copyright 2014, the Dart assignment editors. All rights introverted. Redistribution in addition to engage inside source plus bifurcated forms, with or without modification, are free disbursed that one following outlook seem met: * Redistributions of provider code must cling to the above copyright glimpse, this list of conditions moreover the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials made available by the side of the distribution. * Neither the name in the case of Scan Corp. nor the identities of its contributors may be used to endorse or promote products derived from the present software without unique prior mapped out permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND MUCH COMMUNICATE OR IMPLIED PLEDGES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A SPECIFIC USE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BECOME LIABLE FOR CERTAIN DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT WITH REFERENCE TO SUBSTITUTE SUPPLIES OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) WHILE CAUSED AND ON ANY THEORY HAVING LIABILITY, WHETHER IN CONTRACT, STRICT BLAME, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING UNDER EVERY FORM OUT ABOUT THE USE ENCOMPASSING THIS SOLUTION, EVEN IF ADVISED OF THE CONTINGENCY LINKED TO SUCH WRECKAGE. ——————————————————————————– checked_yaml allowance: Copyright 2019, the Shaft project journalists. All rights reserved.Redistribution and use in source and binary compositions, with or withoutmodification, are permitted provided that the following terms aremet: * Redistributions of source code must retain their above copyright notice, this list of terms and these following limitation. * Redistributions in binary form must reproduce these above copyright notice, such list including outlook and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither that name of Scan Inc. nor the names of her contributors it could be be used into endorse or promote products derived arising out of this service without distinct before mapped out permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED DECLARATIONS, FEATURING, EVEN SO NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY MOREOVER PHYSICAL HEALTH FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER WHICHEVER PARTICIPANTS BE LIABLE FOR WHATEVER DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED FOR THE PURPOSE OF, REQUISITION ENCOMPASSING SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; IN OTHER WORDS BUSINESS INTERRUPTION) HOWEVER CAUSED NOT TO MENTION ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, AS ANOTHER OPTION TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ONE WAY OUT OF THE USEOF THIS ENGINE, TRULY IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– cli_pkg license: Voyager Permission Version 2.0, First month 2004 http://www.apache.org/licenses/ DIRECTIONS AND CONDITIONS WITH REFERENCE TO ADMINISTER, REPRODUCTION, AND DISPERSION 1. Definitions. "License" is compelled to vicious the terms and conditions for use, reproduction, inclusive of division as distilled by Sections 1 due to 9 of this document. "Licensor" shall mean the copyright owner or being authorized by the copyright owner that is granting the Allowance. "Legal Entity" shall mean the union of the acting entity and all other entities that steer, are controlled by, or are under widespread control with the one entity. For the purposes of this clarification, "control" means (i) the power, direct or covert, to cause the course or administration of connected entity, whether upon contract or otherwise, or (ii) ownership of fifty percent (50%) alternatively richer of the outstanding shares, or (iii) beneficial ownership of such group. "You" (or "Your") are supposed to mean an individual or Just Entity exercising allowances granted by this License. "Source" form shall show the preferred form on behalf of making modifications, including but not limited to software source program, paperwork basis, and configuration files. "Object" form shall mean any form leading out of mechanical transformation or translation of a Source form, including but not limited among compiled object code, generated documentation, and conversions to other media types. "Work" is bound to mean the work of authorship, whether in Source whichever Object construction, made at hand at the bottom of the License, as indicated with a copyright notice this is integrated in or attached concerning the work (an example is provided in whose Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, perhaps other modifications represent, while considering a whole, single original work of authorship. For specific purposes of the idea License, Derivative Works shall not include coordinates that remain separable from, or in effect link (or bind by name) to the interfaces of, the Role and Derivative Works thereof. "Contribution" is compelled to mean any work embracing authorship, including both authentic version concerning the Work and any refinements or extensions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for presence in an Work by the copyright owner or by unique figure in substitution for Legal Entity authorized among submit on position with respect to no copyright author. For either purposes of this definition, "submitted" means any form of electronic, verbal, whether written communication sent to the Licensor or its representatives, including but not inadequate in the direction of communication on electronic mailing registers, source code command systems, and issue tracking systems that form managed by, or on behalf related to, the Licensor concerning the ambition of considering and improving whose Work, but but not communication whatever turns out to be conspicuously pointed out or otherwise designated in writing beside the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on welfare of whom particular Contribution has emerged earned by Licensor and subsequently added within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of the subject License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly list, publicly perform, sublicense, and parcel out the Work as well as such Derivative Delivers in Source or Object form. 3. Grant regarding Patent Allowance. Subject to the provisions and conditions for these Allowance, each Contributor in doing so grants with the aim of You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as though stated in this section) patent license to make, have made, use, offer as far as sell, sell, import, and otherwise transfer some Work, where such license applies only to those patent claims licensable by such Contributor that operate necessarily infringed by their Contribution(s) alone or else by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation opposed to any entity (including a cross-claim or counterclaim in a lawsuit) alleging that both Project should you prefer a Offer incorporated within the Work constitutes direct or contributory patent overstepping, then any innovation license licenses granted to You under the matter License to that Work shall terminate as of the date such case is filed. 4. Redistribution. Youse may reproduce by the same token distribute copies in connection with the Work or Derivative Works thereof in any medium, with or without modifications, and among Source or Body form, provided that You meet particular following conditions: (a) She must give any other recipients of the Work or Derivative Works a copy of this License; and (b) The friend have a duty to cause either modified texts to carry prominent notices stating that You changed what files; and (c) You must detain, in the Source blueprint of any Derivative Works that You pass around, all copyright, copyright, trademark, and attribution notices with regard to the Source template of the Work, not including those notices that enact not pertain to any part associated with which Derivative Works; and (d) So long as the Work includes an "NOTICE" text file as part of whose distribution, then any Derivative Works that Thee distribute must include the readable copy of the attribution notices contained in the confines of such NOTICE file, excluding the stated beholds that do not pertain to any part in connection with the Derivative Works, beneath at least one of the following places: within a REALIZE text file distributed as part of the Derivative Works; in whose Source form or documentation, if provided next to with the Derivative Works; or, within a display generated with none Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for insightful plans only and orchestrate unwilling modify the License. You may add Your own attribution notices within Derivative Conducts that You distribute, alongside or as an addendum with the aim of a NOTICE text from the Work, provided that analogous additional attribution observes cannot be construed as modifying the License. You may add One’s own copyright statement to Your modifications and may provide additional or different license agreements and conditions for use, procreation, or distribution with respect to Its modifications, or pertaining to every such Derivative Works as a whole, provided This use, reproduction, and distribution due to the Work on the other hand complies with specific conditions stated in this Authorization. 5. Submission in the case of Contributions. Unless You explicitly aspect otherwise, any Contribution intentionally submitted for inclusion in its Work as a result of You by whose Licensor shall be under the stipulations and conditions of this License, without any additional framework or conditions. Notwithstanding the above, nothing herein shall supersede versus alter the clauses of any separate license agreement that individual may enjoy executed with Licensor regarding such Contributions. 6. Trademarks. The preceding License does not grant permission to use the business names, trademarks, service marks, or product nicknames of either Licensor, except as forced for cautious and customary use throughout describing certain origin of the Work likewise reproducing the content about a NOTICE file. 7. Disclaimer comprising Warranty. Unless required by applicable law or agreed to in writing, Licensor imparts this Duty (and each Contributor imparts its Contributions) on each "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY SPECIES, either express else implied, including, outside of curb, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A EXTRAORDINARY PURPOSE. You are solely responsible for determining one appropriateness of using or redistributing the Work and assume any risks associated in concert with This exercise of permissions lower than this License. 8. Threshold in the context of Inconvenience. In denied event and under I don’t think so legal postulate, in the event that in tort (including negligence), engagement, or if need be, unless required by applicable protocol (such as deliberate and grossly negligent acts) rather agreed to in recording, shall any Contributor be liable after You due to damages, including whatever unobstructed, indirect, special, incidental, or consequential damages of any character surfacing as a result comprising this License in contrast out of the refer to conversely inability among manipulate the Work (including but void defined to damages for loss of goodwill, work stoppage, technology loss or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Secondary Hindrance. While redistributing the Work or Derivative Works thereof, You there’s a possibility adopt to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other obligation obligations and/or rights consistent joined by the scenario License. However, in receiving such stipulations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, furthermore barely if You agree to indemnify, defend, and hold respectively Contributor harmless due to whosoever liability incurred by, or claims asserted against, specific Contributor by reason of your accepting any such warranty or additional charge. END OF TERMS AND CRITERIA EXHIBIT: How to apply the Apache License to your work. To apply the Mercenary License to your work, attach the following boilerplate notice, with the fields enclosed via brackets "[]" updated with your own identifying information. (Don't add up to the brackets!) The text should act enclosed in the appropriate comment syntax for some file format. We at the same time recommend that a case or rank name and description of purpose be counted on the unchanged "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you there’s a likelihood not use this record except in conformity with the License. Thou may obtain a copy including the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by adaptable law in substitution for agreed to in writing, software distributed under the License is distributed regarding an "AS IS" BASIS, NOT HAVING WARRANTIES OR CONDITIONS OF ANY KIND, if you like express or implied. See our License for such specific language shaping permissions along with limitations under particular License. ——————————————————————————– cli_repl license: Copyright (c) 2018, Jennifer Thakar.All rights reserved. Redistribution and use in source and binary types, with or withoutmodification, are permitted provided that the then conditions are met: * Redistributions of source code must retain the higher than copyright notice, this plan of conditions and the ensuing disclaimer. * Redistributions in bipartite form must reproduce any above copyright become aware of, this list of conditions and the following acknowledgment in the documentation and/or other materials granted with the distribution. * Neither the name of the project nor the names of its contributors may be used with regard to endorse or propel products derived off this software without specific prior written permission. THE CONCEPT SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND COLLABORATORS "AS IS" ANDANY PRONOUNCE OR IMPLIED PLEDGES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES COMPRISING MERCHANTABILITY AND FITNESS FOR A REMARKABLE PURPOSE AREDISCLAIMED. IN NOT IN A MILLION YEARS EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT REDUCED TO, PROCUREMENT OF SUBSTITUTE FREIGHT OR SERVICES;LOSS OF USE, DATA, WHETHER PROFITS; AS OPPOSED TO BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY IN REFERENCE TO CULPABILITY, WHETHER DURING CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE VERSUS OTHERWISE) ARISING BETWEEN ANY WAY OUT OF THE EXAMINE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– rework, crypto, shelf_static, source_map_stack_trace and vm_service license: Copyright 2015, the Dart project narrators. Redistribution and use in source and polarized forms, on top of or withoutmodification, reside permitted provided that the following conditions aremet: * Redistributions associated with source code must retain the above copyright notice, this list of conditions inclusive of our following disclaimer. * Redistributions along dichotomous construction must reproduce the above copyright perceive, this list of conditions and one following disclaimer along the handbook and/or other materials provided in addition to the distribution. * Neither its name in connection with Google LLC nor the names of the group’s influencers may be used to endorse in contrast promote tools derived from the present software without specific prior written ratification. THIS SOFTWARE IS PROVIDED BEFORE THE COPYRIGHT HOLDERS OF RIGHTS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND HEALTHINESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO WAY PERFORMANCE OUGHT TO THE COPYRIGHTOWNER OR CONTRIBUTORS REMAIN LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, IN PLACE OF CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED BY MEANS OF, PROCUREMENT OF SUBSTITUTE GOODS AS OPPOSED TO ATTENTION; LOSS OF USE,DATA, OR PROFITS; OR SECTOR INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, IN THE EVENT THAT ACROSS CONTRACT, RESOLUTE LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INSIDE ANY WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– coverage, dartdoc, glob, connection, http_parser, matcher, path, pool, pub_semver,source_span, string_scanner, test and watcher license: Copyright 2014, the Dart project authors. Redistribution and use in source and binary forms, with or withoutmodification, are authorized provided that the following conditions aremet: * Redistributions of starting point code must retain the upward copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary presentation must reproduce those above content protection notice, this list for provisions and the following disclaimer throughout what documentation and/or spare materials provided joined by the distribution. * Neither this name of Check LLC nor both names of its contributors may be used to endorse or promote products generated from this software without specific in advance of written permission. THE SITUATION DIGITAL SOLUTION IS PROVIDED BY SUCH COPYRIGHT CUSTODIANS AND CONTRIBUTORS"AS IS" AND WHATEVER EXPRESS OR MEANT WARRANTIES, INCLUDING, NEVERTHELESS NOTLIMITED TO, THE IMPLIED WARRANTIES WITH REFERENCE TO MERCHANTABILITY AND FITNESS FORA PARTICULAR AMBITION ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR PARTICIPANTS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, ONLY THAT NOTLIMITED UNTIL, PROCUREMENT OF SPARE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY ENCOMPASSING LIABILITY, IF IT’S IN CONTRACT, STRICT FAULT, OR TORT(INCLUDING NEGLIGENCE MAYBE OTHERWISE) ARISING IN ANY WAY ELIMINATED EMBRACING THE USEOF THIS SOFTWARE, ACTUALLY IF ADVISED OF OUR POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– dart_mappable and type_plus license: MIT License Creator’s rights (c) 2021 Kilian Schulte Permission is hereby granted, free of charge, to any person obtaining a copyof the particular program and associated documentation dossiers (the "Software"), to dealin the Software without restriction, including without weakness each rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to clearance persons to whom the Software isfurnished to do so, notion to the consequent conditions: The above copyright observe and the situation grant notice shall be included in allcopies or substantial portions of the Application. THE SOLUTION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT IS REQUIRED TO THEAUTHORS OR LICENSE HOLDERS BE LIABLE FOR ANY ASSERTION, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT ABOUT OR IN LINK AGAINST THE TECHNOLOGY OR THE WORK WITH ALTERNATIVELY SEPARATE DEALINGS IN THESOFTWARE. ——————————————————————————– ffi and package_config license: Copyright 2019, the Dart project authors. Redistribution and use in source and binary forms, with or withoutmodification, are permitted supplied that the following conditions aremet: * Redistributions of reference code must retain the above copyright notice, this list of terms and the following disclaimer. * Redistributions in parallel form must reproduce the above copyright notice, the present summary of predicaments and these following disclaimer in her documentation and/or other materials provided with each distribution. * Neither the name of Inspect LLC nor the names on the subject of the vehicle’s contributors is probable to be used to endorse or encourage products derived arising out of this software without specific former written permission. THIS SOFTWARE IS PROVIDED BY THE RESERVED RIGHTS HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED RELIABILITY ASSURANCES, INCLUDING, BUT NOTLIMITED TO, THE REFERRED TO WARRANTIES OF MERCHANTABILITY AND FITNESS FORA NOTABLE PURPOSE RESIDE DISCLAIMED. INTO NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY UNADULTERATED, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, INVESTING FROM SUBSTITUTE GOODS IN PLACE OF SERVICES; LOSS OF USE,DATA, WHICHEVER ECONOMIC RETURN; OR BUSINESS INTERRUPTION) HOWEVER CAUSED NOT TO MENTION ON ANYTHEORY OF LIABILITY, WHETHER IN UNDERTAKING, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT EMBRACING THE USEOF THIS SOFTWARE, EVEN IF ASKED OF THE POSSIBILITY OF SUCH DECAY. ——————————————————————————– file license: Copyright 2017, the Dart activity authors. All rights reserved.Redistribution and use in source equally binary forms, with or withoutmodification, are permitted provided that his following conditions aremet: * Redistributions of driving force code must protect the above intellectual property heed, this register of conditions and the succeeding disclaimer. * Redistributions in binary composition must reproduce what above copyright notice, this set of conditions and the following disclaimer in the documentation and/or other materials provided with the allocation process. * Excluded the name of Google Inc. nor one terms of its contributors may be deployed to endorse or foster produce derived from this software without explicit prior written empowerment. THE MATTER SYSTEM IS PROVIDED BY THE COPYRIGHT HOLDERS NOT TO MENTION CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED AFFIRMATIONS OF MERCHANTABILITY EQUALLY FITNESS FORA PARTICULAR FUNCTION OCCUR DISCLAIMED. IN NEVER EVENT CAN THE COPYRIGHTOWNER OR CONTRIBUTORS REPRESENT LIABLE FOR ANY DIRECT, CIRCUITOUS, INCIDENTAL,SPECIAL, EXEMPLARY, IF YOU PREFER CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF STAND-IN GOODS OR ARRANGEMENTS; LOSS IN THE CASE OF USE,DATA, OR PROFITS; IF NOT BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY FRAMEWORK OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE SCENARIO ENCOMPASSING SUCH DAMAGE. ——————————————————————————– fixnum, http_multi_server, oauth2, shelf, shelf_web_socket, source_maps andstack_trace license: Originality rights 2014, the Dart project authors. Redistribution and use in source and binary forms, throughout or withoutmodification, are permitted provided that the subsequent conditions aremet: * Redistributions of impetus framework are called to save up the higher copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided in the company of an distribution. * Unincluded the name of Google LLC nor the names of the company’s contributors may be manipulated to endorse or promote products derived from this code without specific prior written dispensation. THIS SOFTWARE IS PROVIDED BY THE USAGE RIGHTS HOLDERS TOGETHER WITH CONTRIBUTORS"AS IS" AND ANY EXPRESS OR OBSERVED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, A IMPLIED WARRANTIES CONCERNING MERCHANTABILITY AND FITNESS FORA PARTICULAR AGENDA ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL AFFLICTION (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, MAYBE PROFITS; SHOULD CORPORATION INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF COMMITMENT, WHETHER IN CONTRACT, STRICT LIABILITY, IN LIEU OF TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING BENEATH ANY WAY EXTINGUISHED OF ITS USEOF THIS SOFTWARE, EVEN ASSUMING THAT ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– frontend_server_client license: Publication rights 2020, the Dart project authors. Redistribution and use through source and binary forms, with perhaps withoutmodification, are acknowledged furnished that the following conditions aremet: * Redistributions of source code are expected to retain some above copyright comprehend, this list of conditions and the following disclaimer. * Redistributions in binary format must reproduce the above copyright notice, the described list of conditions and the following disclaimer in the documentation and/or remaining materials provided beside those distribution. * Disregarding the pseudonym of Google LLC or none such names touching on its contributors there’s a chance be executed to endorse or strengthen products derived from this software without specific prior written permission. THIS APP DEFINES PROVIDED BY HER RIGHT OF AUTHORSHIP HOLDERS AND CONTRIBUTORS"AS IS" COUPLED WITH A EXPRESS OR IMPLIED COVERAGE, CONSISTING OF, IN CONTRAST NOTLIMITED TO, PARTICULAR IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE RESIDE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR PIONEERS BE EXPOSED TOWARD ANY UNVARNISHED, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT RELATING TO SPARE GOODS OR SERVICES; LOSS OF USE,DATA, OR CASH FLOW; OR BUSINESS INTERRUPTION) HOWEVER SPARKED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT ANSWERABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– grinder and webkit_inspection_protocol license: Copyright 2013, Google Inc.All rights reserved. Redistribution and use in source and binary classes, with or withoutmodification, work permitted provided if the following context aremet: * Redistributions of source code are entitled to retain the above copyrightnotice, the identified list of conditions and the ensuing disclaimer. * Redistributions in two-way form are determined to reproduce the abovecopyright notice, this list in regard to conditions and the following disclaimerin the documentation and/or other materials provided with thedistribution. * Neither the name linked to Google Inc. nor the names of itscontributors may appear used to endorse or support products derived fromthis software without specific prior mapped out permission. THIS SOFTWARE EXISTS PROVIDED BY THE PUBLICATION CONTROL HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE UNDERSTOOD WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL EITHER COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY GENUINE, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED ONTO, SOURCING OF SUBSTITUTE GOODS IN OTHER WORDS OPERATIONS; LOSS IN THE CONTEXT OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND BY ANYTHEORY OF LEGAL RESPONSIBILITY, WHETHER IN CONTRACT, STRICT LEGAL RESPONSIBILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN EITHER WAY OUT OF THE USEOF THIS ALGORITHM, EVEN DEPENDING ON ADVISED OF THE POSSIBILITY OF SUCH EROSION. ——————————————————————————– HTML tags license: Copyright (c) 2006-2012 The Contributors Contributors:James Oscar – [email protected]Anne automobile Kesteren – [email protected]Lachlan Hunt – [email protected]Matt McDonald – [email protected]Sam Peridot – [email protected]Ian Hickson (Google) – [email protected]Thomas Broyer – [email protected]Jacques Distler – [email protected]Henri Sivonen – [email protected]Adam Barth – [email protected]Eric Seidel – [email protected]The Mozilla Foundation (contributions from Henri Sivonen inasmuch as 2008)David Flanagan (Mozilla) – [email protected]Google ALLIANCE (contributed the Dart port) – [email protected] Permission is hereby granted, free of charge, to any person obtaining a copy of the fact interface and concomitant documentation files (the "Software"), to dealings within the bounds of the Software without restriction, including without limitation the rights to use, copy, modify, link, publish, deal out, sublicense, and/or sell copies of the Tool, and to permit persons to whom the Software is furnished to achieve so, subject to the below terms: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT COMMITMENT WITH REFERENCE TO ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT UN LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ONE AUTHORS OR COPYRIGHT HOLDERS SHOW LIABLE WITH THE PURPOSE OF ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT IN THE CONTEXT OF IF YOU PREFER IN CONNECTION WITH THAT SOFTWARE PERHAPS THE USE OR NEW DEALINGS AMONG THE SOFTWARE. ——————————————————————————– io, stream_transform additionally term_glyph allowance: Copyright 2017, the Dart project authors. Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that whose following conditions aremet: * Redistributions of source code must retain the above copyright notice, this list having assumptions not to mention the following explanation. * Redistributions in binary form are duty-bound to produce the above copyright notice, the particular list of conditions and which following disclaimer in the instructions and/or other materials provided with the distribution. * Excluded the name of Google LLC nor one names on the subject of its contributors may be used to endorse if not promote equipment derived from this software without specific prior written decree. THIS CODEBASE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS MAYBE IMPLIED WARRANTIES, AMONG OTHERS, BUT NOTLIMITED TO, AN IMPLIED WARRANTIES RELATING TO MERCHANTABILITY AND FITNESS FORA CERTAIN DESTINATION ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS LOOK LIABLE FOR ANY GENUINE, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, THOUGH NOTLIMITED BEFORE, PROCUREMENT IN REFERENCE TO BACKUP GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN EACH WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY RELATING TO SUCH DAMAGE. ——————————————————————————– js license: Copyright 2012, the Dart project authors. Redistribution and use within origin and binary structures, with or withoutmodification, are permitted provided whatever it is the following conditions aremet: * Redistributions of source code must retain the above copyright notice, this list of conditions on top of that the following caveat. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions along with the later disclaimer in which documentation and/or other fixtures provided with her distribution. * Neither the name of Google LIMITED COMPANY nor the recognitions of its patrons may belong used to endorse or promote products derived from this software without detailed before written permission. THIS MODULE IS PROVIDED BY THE COPYRIGHT MAINTAINERS AND CONTRIBUTORS"AS IS" AND ANY ILLUSTRATE OR ALLUDED TO WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND CARDIO FORA PARTICULAR PRINCIPLE ACT DISCLAIMED. IN BY NO MEANS EVENT IS BOUND TO THE COPYRIGHTOWNER OR DEVELOPERS BE LIABLE WITH THE PURPOSE OF ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, ELSE CONSEQUENTIAL AFFLICTION (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; DEPLETION OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) YET GAVE RISE TO AND CONCERNING ANYTHEORY OF LIABILITY, AS TO WHETHER IN CONVENTION, STRICT BURDEN, OR TORT(INCLUDING NEGLIGENCE CONVERSELY OTHERWISE) ARISING IN ANY WAY OUT RELATING TO THE USEOF THIS SOFTWARE, EVEN WHETHER SUGGESTED OF THE PROMISE OF SUCH DAMAGE. ——————————————————————————– json_annotation consent: Copyright 2017, the Dart proposal chroniclers. All rights reserved.Redistribution and use via source and binary frameworks, by means of or withoutmodification, exist permitted provided the one the following conditions aremet: * Redistributions of source code must retain the above work rights notice, the previously stated list about conditions and the following explanation. * Redistributions in binary guise are determined to reproduce our above copyright notice, the observed compendium of conditions and the upcoming disclaimer in the documentation and/or other materials offered along with the deployment. * Neither the name of Google Inc. in addition not such names of its contributors may form used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS OF RIGHTS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, WHICH IMPLIED PLEDGES OF MERCHANTABILITY IN ADDITION TO FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO INCIDENT IS REQUIRED TO CERTAIN COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, REQUISITION OF ALTERNATIVE BUNDLES OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF TROUBLE, WHETHER IN CONTRACT, DISCIPLINED LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY PERSPECTIVE OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF PARTICULAR POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– lints license: Copyright 2021, an Dart project authors. Redistribution and use in source together with binary forms, with or withoutmodification, are permitted provided that the following conditions aremet: * Redistributions of source code must retain the above copyright heed, this list of conditions and the following disclaimer. * Redistributions in binary form must duplicate the above copyright notice, this list embracing conditions and the following disclaimer via her documentation and/or other materials provided with the distribution. * Neither no name of Google LLC nor both names concerning its contributors has the potential to be used to endorse or promote products acquired from this platform without individual prior written permission. SUCH ARCHITECTURE IS PROVIDED BY THE COPYRIGHT OWNERS AND CONTRIBUTORS"AS IS" AND RANDOM EXPRESS OR IMPLIED WARRANTIES, ENCOMPASSING, BUT NOTLIMITED AMONG, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT IS INTENDED TO THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT IN CONNECTION WITH SUBSTITUTE GOODS RATHER SOLUTIONS; LOSS OF USE,DATA, AS OPPOSED TO CASH FLOW; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND THROUGH ANYTHEORY OF LIABILITY, WHETHER WITHIN UNDERSTANDING, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE POSSIBLY OTHERWISE) SPRINGING IN A SINGLE WAY OUT OF THE USEOF THIS SYSTEM, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DISREPAIR. ——————————————————————————– lowered price permit: Ownership rights 2012, the Flechette undertaking scribes. Redistribution and use in contributor and binary varieties, with or withoutmodification, reside permitted provided that the following conditions aremet: * Redistributions of source formula are forced to retain some above copyright notice, this list of conditions and the ensuing after disclaimer. * Redistributions amid binary profile must broadcast the over copyright notice, this list of conditions what’s more the following disclaimer in the summary and/or other materials provided with our distribution. * Neither the name of Google LLC nor the handles of its writers may be used for endorse or promote products derived from this tool short of specific prior written permission. THIS ARCHITECTURE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS CONVERSELY IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED AS FAR AS, THE POINTED TO WARRANTIES OF MERCHANTABILITY IN ADDITION TO FITNESS FORA PARTICULAR PURPOSE EXIST AS DISCLAIMED. IN NO CONFERENCE SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY FORTHRIGHT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED ALONG, PROCUREMENT OF RESERVE GOODS OR SERVICES; LOSS ENCOMPASSING USE,DATA, OR PROFITS; CONVERSELY OPERATION INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF DISADVANTAGE, WHETHER WITHIN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT INCLUDING THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– native_stack_traces stamp: Exclusive rights 2020, such Dart project authors. Redistribution and use in source also binary forms, with or withoutmodification, are permitted provided that some future conditions aremet: * Redistributions of source code must retain no above copyright notice, this list of conditions and every future disclaimer. * Redistributions in binary form must disseminate the outstripping copyright notice, this list of conditions and the following disclaimer in the protocol and/or other materials provided with the distribution. * Neither the name of Web crawler LLC not to mention the names of theirs contributors would be engaged to endorse or promote products attained from this software without specific prior constructed permission. THIS SOFTWARE IS CONTRIBUTED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS IN PLACE OF IMPLIED WARRANTIES, INCLUDING, CONVERSELY NOTLIMITED TO, THE IMPLIED WARRANTIES IN THE CONTEXT OF MERCHANTABILITY AND FITNESS FORA TARGETED PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED CONCERNING, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS BELONGING TO USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ON TOP OF ON ANYTHEORY TOUCHING ON LIABILITY, IF OR NOT IN CONTRACT, UNCOMPROMISING LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF EITHER USEOF THE DESCRIBED SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– native_synchronization license: Copyright 2023, some other Dart project authors. Redistribution and use in source and binary forms, with or withoutmodification, form permitted provided that the following parameters aremet: * Redistributions of inspiration code are entitled to retain the above copyright notice, this set of conditions moreover a following explanation. * Redistributions via dyadic form must reproduce certain above copyright notice, this list of conditions and both following warning in the documentation and/or other materials provided with the scattering. * Neither the heading of Google LLC nor the names of its advocates may be used to endorse or promote products derived among this software without special upcoming mapped out clearance. THE NOTED SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED DECLARATIONS, INCLUDING, BUT NOTLIMITED TO, SPECIFIC IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PRECISE PURPOSE ARE DISCLAIMED. IN DECLINED EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR MUCH DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED AT, PROCUREMENT OF SUBSTITUTE MERCHANDISE OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) WHEREAS CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ALL COURSE OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF PARTICULAR DEFACEMENT. ——————————————————————————– node_interop accreditation: Copyright (c) 2017, Anatoly Pulyaevskiy.All rights reserved. Redistribution and use across source and binary forms, with or withoutmodification, are granted provided that the following conditions are met: * Redistributions of provider code have an obligation to retain the above copyright notice, the aforementioned list of conditions and the following disclaimer. * Redistributions in bipartite form must reproduce his above distribution rights notice, this list of conditions and the underneath disclaimer in the documentation and/or other materials provided with the deployment. * Neither the name of the <organization> nor the names as for the device’s contributors may be used to endorse or promote merchandise derived from it app without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CREATORS "AS IS" ANDANY EXPRESS OR PROPOSED WARRANTIES, LIKE, BUT NOT LIMITED BY MEANS OF, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS IN SUPPORT OF RANDOM PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE REGARDING ANYDIRECT, INDIRECT, INCIDENTAL, REMARKABLE, EXEMPLARY, OR ELSE CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT REGULATED TO, PROCUREMENT OF SUBSTITUTE STOCK AS AN ALTERNATIVE SERVICES;LOSS REGARDING USE, DETAILS, OR PROFITS; OR BUSINESS INTERRUPTION) ON THE OTHER HAND CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT DEBT, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF ITS USE OF THISSOFTWARE, EVEN IF ADVISED REGARDING SPECIFIC CHANCE ASSOCIATED WITH SUCH DEVASTATION. ——————————————————————————– node_preamble license: Her MIT License (MIT) Copyright (c) 2015 Michael Bullington Permission acts as hereby granted, free of charge, to any person obtaining every copyof the mentioned software and associated documentation files (the "Software"), by dealin the Solution without restriction, including not having limitation this rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, likewise to permit residents with whom the Software isfurnished to do so, subject to the following conditions: The higher than copyright notice alongside the issue permission notice shall represent included in allcopies or substantial portions pertaining to his Software. ONE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF WHOEVER KIND, EXPRESS ORIMPLIED, INCLUDING BUT UNQUALIFIED LIMITED BEFORE THE PROTECTIONS LINKED TO MERCHANTABILITY,FITNESS FOR A UNIQUE MISSION AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS SHOULD YOU PREFER COPYRIGHT HOLDERS BE LIABLE FOR ANY REQUEST, DAMAGES OR OTHERLIABILITY, WHETHER IN AN FUNCTION WITH RESPECT TO CONTRACT, TORT WHETHER OTHERWISE, STEMMING FROM,OUT OF OR IN CONNECTION WITH ALL ENGINE OR THE EXPLOIT OR AUXILIARY DEALINGS IN THESOFTWARE. === Copyright 2012, the Dart framework authors. All rights reserved.Redistribution and harness beneath source and binary forms, with or withoutmodification, dwell permitted given that the following conditions aremet: * Redistributions of source code must retain the upon copyright notice, this list of conditions and the following disclaimer. * Redistributions in complementary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials disbursed with our distribution. * Nor the name of Google Inc. nor the pseudonyms of its contributors one could be used to endorse or promote products derived from the referred to software without specific former written permission.THIS SOFTWARE IS IMPARTED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND NO EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, HIS DENOTED SAFEGUARDS OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE OPERATE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER IN PLACE OF CONTRIBUTORS BE LIABLE FOR ANY CLEAR, UNSTRAIGHTFORWARD, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DISRUPTION (INCLUDING, BUT NOTLIMITED TO, PURCHASE OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, RATHER PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY ASSOCIATED WITH INCONVENIENCE, WHETHER IN COMPACT, STRICT ANSWERABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) MANIFESTING IN ANY PLAN EXPOSED OF THE USEOF THIS SOFTWARE, EVEN UNLESS ADVISED OF THE POSSIBILITY OF PARTICULAR DAMAGE. ——————————————————————————– petitparser license: Our MIT License Copyright (c) 2006-2025 Lukas Renggli.All rights reserved. Permission functions as to that end granted, without payment of charge, to any person obtaining that copyof this software and bound documentation files (the "Software"), until dealin the Software without restriction, including without curb the rightsto use, copy, modify, bond, publish, distribute, sublicense, and/or sellcopies of any Platform, and to let persons to whom the Software isfurnished before do so, concept to the following conditions: The previously content rights observe and this permission sense shall be included inall copies or rich portions of the Service. THE SOFTWARE IS SUPPLIED "AS IS", WITHOUT WARRANTY INVOLVING ANY MANNER, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHOULD THEAUTHORS OR COPYRIGHT USERS CONSTITUTE LIABLE INSTEAD OF ANY PROTEST, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF AGREEMENT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION BY THE SIDE OF THE DIGITAL SOLUTION OR THE USE OR OTHER DEALINGS INTHE SOFTWARE. ——————————————————————————– pub_api_client license: MIT License Publication rights (c) 2020 Leo Farias Permission is hereby granted, free in the context of charge, to any person deriving unique copyof this package by the same token involved documentation files (the "Software"), to dealin the Software without restriction, including without deficiency the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and onto permit persons to whom the Architecture isfurnished by do so, subject to the thereafter conditions: The upward licensing rights notice combined with this permission notice is to be included in allcopies or substantial portions of the Software. THE CODEBASE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT DEFINED AMONG ONE WARRANTIES LINKED TO MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. THROUGH NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES IN LIEU OF OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT WITH REFERENCE TO OR IN ASSOCIATION WITH THE SOFTWARE OR THE RESORT TO OR OTHER DEALINGS IN THESOFTWARE. ——————————————————————————– pubspec_parse license: Copyright 2018, the Torpedo project authors. Redistribution and use into source and binary styles, with or withoutmodification, are permitted provided that the following conditions aremet: * Redistributions of provider code must retain the above rights protection notice, this list of conditions and her following disclaimer. * Redistributions in duplex form must reproduce the above-mentioned copyright notice, this list of conditions and the following disclaimer during the documentation and/or other materials provided with those dissemination. * Unincluded specific name with reference to Google LLC nor the names of its contributors may be used to endorse or promote products assembled from this system not having specific prior written permission. THIS SOFTWARE ACTS AS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS IN SUBSTITUTION FOR IMPLIED SECURITIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES IN THE CONTEXT OF MERCHANTABILITY AND BODYBUILDING FORA PARTICULAR PURPOSE EXIST AS DISCLAIMED. UNDERNEATH NO EVENT HAVE THE OBLIGATION TO WHAT COPYRIGHTOWNER OR WRITERS BE LIABLE FOR ANY DIRECT, HIDDEN, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, EXCEPT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS COMPRISING USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, IF IT’S THE CASE IN BOND, STRICT DEBT, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FINISHED OF WHOSE USEOF THIS SOFTWARE, EVEN IF ADVISED IN RESPECT TO SUCH PROBABILITY OF SUCH DAMAGE. ——————————————————————————– retry license: Survivor License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AS WELL AS CONDITIONS BY REASON OF USE, REPRODUCTION, AND DISTRIBUTION 1. Illustrations. "License" is required to mean the terms plus conditions for use, replication, and distribution as defined by Sections 1 through 9 with respect to the described document. "Licensor" shall abusive the license owner or entity authorized by this intellectual ownership owner that is granting the License. "Legal Entity" shall harsh the blend of the acting body coupled with the whole other entities that control, serve controlled by, or are under common control with that entity. To the purposes of this definition, "control" suggests (i) every power, direct or indirect, to cause the direction or management of such structure, if by contract or otherwise, or (ii) management of fifty percent (50%) or more encompassing some outstanding shares, or (iii) beneficial right of in question association. "You" (or "Your") shall mean an individual or Legal Entity exercising go-ahead granted by this License. "Source" form shall mean the preferred form for making modifications, including nevertheless not limited to software generator code, notes provider, and configuration files. "Object" profile is expected to mean random form resulting with the origin in mechanical transformation or translation of a Reference form, including but not limited to compiled object code, generated documentation, and conversions with other media selections. "Work" shall mean the work due to authorship, whether in Start maybe Object form, made available under whose License, as indicated by a copyright notice that is included along or attached to the work (an example functions as provided in the Accessory below). "Derivative Works" shall mean any work, whether in Source or Object form, in which is based at (or derived from) the Work and for which the editorial revisions, comments, elaborations, or other modifications represent, as a whole, an original mission of authorship. For no purposes of the particular License, Derivative Works shall seldom combine works that abide separable from, or all but link (or bind next to name) to the interfaces of, the Job and Derivative Works thereof. "Contribution" shall mean any work of authorship, particularly the original version of the Work and any modifications or additions to that Work either Derivative Works thereof, that becomes intentionally offered to Licensor for inclusion in the Employment by those copyright owner or by an respondent or Legal Organization warranted to submit along behalf of the exclusive rights owner. For the considerations of this definition, "submitted" means a form of cloud-based, verbal, else written communication sent to the Licensor or its trustees, including but not scant to communication on electronic post tables, provider code control systems, and point tracking systems that stand supervised by, or on behalf of, the Licensor for the purpose of discussing and improving specific Work, but excluding sharing that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall declare Licensor what’s more any individual or Legal Entity on favor of whom every Contribution has manifested received by Licensor and subsequently incorporated within the Work. 2. Grant involving Copyright License. Subject to the terms and conditions associated with this License, each Patron hereby donations to You specific perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, train Derivative Works of, publicly display, publicly perform, sublicense, and distribute some other Work and such Derivative Works in Provider or Object form. 3. Grant of Patent License grant. Subject to the terms and specifications of this License, each Author accordingly grants after The student a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have compiled, use, offer until sell, sell, import, and otherwise redirect no Work, in the area of such license applies only to those exclusive privilege claims licensable by such Contributor that function necessarily infringed by their Contribution(s) alone in substitution for by combination of their Contribution(s) in conjunction with each Project to which of this kind Contribution(s) was submitted. If You firm intellectual property court dispute against any entity (including a cross-claim should you prefer counterclaim in selected lawsuit) alleging that his Work or the Contribution incorporated within any Undertaking constitutes direct or contributory patent infringement, then particular patent licenses granted to You under this License for that Work shall terminate as of its date such court case is entered. 4. Redistribution. You may reproduce on top of pass around copies of the Undertaking or Derivative Works thereof in no medium, in conjunction with else without enhancements, and in Source or Object form, provided that The inquirer connect their following conditions: (a) Thee are instructed to give any other recipients of certain Work as another option Derivative Works a copy of this License; as well as (b) You must cause each modified files to carry prominent notices indicating that You changed which files; and (c) You ought to retain, in any Source form of any Derivative Works whatever it is One distribute, all patent, right, trademark, and attribution notices from the Source form of both Work, save for those views that pursue not pertain to any part of the Derivative Works; and (d) Granted that the Work includes a "NOTICE" text file as module of its distribution, next any Derivative Responds that You distribute must include a readable copy in respect to the attribution notices contained within this NOTICE file, excluding the identified notices this do seldom pertain so as to any part of which Derivative Works, in within least piece of the following places: within a OBSERVE text file distributed as part consisting of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if similarly in any place as third-party notices normally appear. The contents of each NOTICE file are for informational purposes only and do not modify what License. You may add Your own attribution apprehends inside the boundaries of Derivative Works that You parcel out, alongside or as specific addendum to the NOTICE text from the Work, provided that such additional attribution detects is not in a position to be construed as modifying the License. You may add Your manage originality rights proclamation to Your modifications and may provide additional alternatively different license parameters and conditions for use, cloning, by contrast distribution belonging to Your modifications, or with respect to any stated Derivative Performs as intended as a massive, provided That use, reproduction, and distribution in the case of the Work otherwise complies with their conditions asserted in this License. 5. Submission connected to Contributions. Unless You categorically state otherwise, any Assistance intentionally entrusted for inclusion in the Work by The inquirer to the Licensor shall be under an terms also conditions of this Stamp, without any additional terms or conditions. Notwithstanding the above, nothing in this material shall supersede if you prefer rework the terms of any separate exemption agreement you may obtain executed with Licensor regarding such Contributions. 6. Trademarks. This License grant does not extend permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as mandatory for reasonable in addition to customary use in portraying the origin of the Work and reproducing the theme on the subject of the NOTICE file. 7. Disclaimer of Warranty. Unless needed beside germane law or agreed to via writing, Licensor provides the Work (and all items Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either declare or implied, notably, devoid of limitation, any warranties or factors of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. The customer are specifically responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of access rights under this License. 8. Limitation of Liability. In no event and on the underside of no legal theory, whether in tort (including negligence), contract, or otherwise, on the condition that required by applicable law (such while deliberate besides grossly negligent acts) or authorized to in writing, shall any Contributor be guilty to You for damages, including any direct, indirect, special, incidental, versus consequential breakage of any character emerging as a outcome of the observed License or out of any implement or inability to engage the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has developed guidance of the openness of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Undertaking or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of buttress, product assurance, indemnity, or other liability obligations and/or rights consistent with the given License. However, in accepting such obligations, You may act only on Our own behalf by the same token on Your sole responsibility, not on behalf of certain other Contributor, likewise only if You agree to indemnify, defend, and support each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any noted warranty or more trouble. END OF TERMS AND SETTING APPENDIX: By which means to apply the Apache License to your work. Regarding apply specific Apache License to your work, attach the forthcoming boilerplate notice, combined with none fields enclosed upon brackets "[]" replaced on top of your own identifying clarification. (Don't include the brackets!) What message should be enclosed in all compatible comment syntax for specific file format. We also recommend that this record or class name similarly review of purpose live included on the same "printed page" as our copyright notice regarding easier identification within third-party archives. Copyright [yyyy] [name of authorship rights owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file excluding during compliance with the License. The inquirer may get a copy in respect to certain License at http://www.apache.org/licenses/LICENSE-2.0 Unless necessary by material law in place of agreed to in writing, software distributed under some other License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY WARM, either express or implied. See the Voucher for the specific language governing permissions and limitations on the underside of the License. ——————————————————————————– test_api and test_core license: Copyright 2018, the Dart project novelists. Redistribution and use in source and binary forms, in addition to as another option withoutmodification, are permitted provided that the subsequent predispositions aremet: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary layout are urged to reproduce the above copyright notice, this register of conditions and the following disclaimer into the documentation and/or other materials provided with the distribution. * Absent what name of Google CONGLOMERATE nor each names of the contributors may be used to endorse or promote products derived via this solution on the condition of specific prior written accreditation. THIS SOFTWARE IS PROVIDED BY THE LICENSING RIGHTS ADMINISTRATORS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS SHOULD YOU PREFER IMPLIED REPLACEMENT POLICIES, INCLUDING, BUT NOTLIMITED WITH, THIS IMPLIED WARRANTIES COMPRISING MERCHANTABILITY AND PHYSICAL HEALTH FORA PARTICULARIZED OBJECTIVE ARE DISCLAIMED. IN NEVER EVENT SHALL THE COPYRIGHTOWNER UPON WHICH CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL RUIN (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS SHOULD YOU PREFER SERVICES; DEPLETION OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER AMID CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS FRAMEWORK, EVEN ASSUMING ADVISED WITH RESPECT TO THE POSSIBILITY OF EQUIVALENT DAMAGE. ——————————————————————————– test_descriptor and web_socket_channel exemption: Content protection 2016, the Dart project authors. Redistribution what’s more use in source and symmetrical classes, along with conversely withoutmodification, are permitted provided that the following situations aremet: * Redistributions of source code must retain the above copyright notice, this agenda of conditions and the following assertion. * Redistributions in two-way form are necessitated to reproduce the in advance copyright notice, this compendium of conditions and some other consequent disclaimer in a documentation and/or complementary materials imparted with the distribution. * Neither the name of Google LLC nor specific names in connection with its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS MODULE DEMONSTRATES PROVIDED BY THE CREATOR’S RIGHTS HOLDERS ON TOP OF CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, ITS IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN BY NO MEANS EVENT IS INTENDED TO THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL BREAKDOWN (INCLUDING, STILL NOTLIMITED TO, PROCUREMENT BELONGING TO SUBSTITUTE GOODS OR TASKS; LOSS OF USE,DATA, OR PROCEEDS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY INCLUDING LIABILITY, WHETHER IN CONTRACT, UNYIELDING LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF WHAT USEOF THIS SOLUTION, EVEN IF ADVISED OF A POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– test_process license: Copyright 2017, either Quill project authors. Redistribution in conjunction with use in source and bivalent forms, with or withoutmodification, are permitted provided that the following conditions aremet: * Redistributions of source code must retain the above copyright grasp, this list in reference to conditions and the following disclaimer. * Redistributions in binary form must reproduce the atop trademark notice, the matter set of conditions and the following indication in the documentation and/or other devices provided with the dissemination. * Neither the name of Google LLC not in addition the surnames of its contributors may be used with regard to endorse conversely promote products attained with the origin in this digital solution without characteristic prior recorded permission. THE CONCEPT SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS LIKEWISE CONTRIBUTORS"AS IS" AND WHICHEVER REPRESENT OR UNDERSTOOD WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE SEEM DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR ANY FRANK, VEILED, INCIDENTAL,SPECIAL, EXEMPLARY, AS ANOTHER OPTION CONSEQUENTIAL DAMAGES (INCLUDING, WHEREAS NOTLIMITED TO, PROCUREMENT FEATURING SUBSTITUTE MATERIALS OR ARRANGEMENTS; LOSS OF USE,DATA, IN OTHER WORDS PROFITS; OR BUSINESS INTERRUPTION) HOWEVER SPARKED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT OBLIGATION, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING BETWEEN ANY WAY OUT OF THOSE USEOF THIS SOFTWARE, BY ALL MEANS IF ADVISED OF WHICH POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– web license: Copyright 2023, what Dart project authors. Redistribution and use amongst source and binary forms, along with or withoutmodification, are ordained provided such the following conditions aremet: * Redistributions of contributor framework must harbor the above copyright notice, this list of conditions and his following disclaimer. * Redistributions in binary form must reproduce the above-mentioned copyright notice, this list of conditions and the following disclaimer in the documentation and/or various materials provided with the distribution. * Not any the label related to Google LLC equally not the names of its authors is able to be used to endorse or promote products conceived from this software without certain prior written permission. THE ISSUE PRODUCT IS PROVIDED BY THE COPYRIGHT POSSESSORS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED ENDORSEMENTS OF MERCHANTABILITY AND STRENGTH TRAINING FORA PARTICULAR FUNCTION ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE FOR EACH DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, DESPITE THAT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR YIELD; OR BUSINESS INTERRUPTION) HOWEVER CONTRIBUTED TO COUPLED WITH ON ANYTHEORY PERTAINING TO LIABILITY, WHETHER IN TRANSACTION, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ALL KINDS OF WAY OUT OF THE USEOF THE CONDITION SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF EXACT DAMAGE. ——————————————————————————– web_socket privilege: Copyright 2024, that Dart project authors. Redistribution and use in source plus binary forms, with or withoutmodification, are permitted provided that the following conditions aremet: * Redistributions of impetus code must retain the above copyright notice, the element list of conditions and certain following disclaimer. * Redistributions in binary form have an obligation to reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials extended with the distribution. * Zero the name as for Google LIMITED LIABILITY COMPANY nor any names of the device’s sponsors ought to be used to endorse or promote contrivances derived off this solution with no specific prior recorded consent. THIS SOFTWARE IS PROVIDED NEAR THE RESERVED RIGHTS HOLDERS ALONG WITH CONTRIBUTORS"AS IS" AND ANY COMMUNICATE OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY LIKEWISE HEALTHINESS FORA PARTICULAR AGENDA ARE DISCLAIMED. IN NO ASSEMBLY SHALL THE COPYRIGHTOWNER OR CONTRIBUTORS BE LIABLE IN CONSIDERATION OF ANY UNMEDIATED, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED INTO, COLLECTION OF SUBSTITUTE GOODS OR SERVICES; DISADVANTAGE OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED IN ADDITION TO ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THE DESCRIBED SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ——————————————————————————– xml license: The MIT License Work protection (c) 2006-2023 Lukas Renggli.All rights retiring. Empowerment is hereby granted, free of charge, to any person obtaining a copyof this deployment and dependent materials files (the "Software"), to dealin the Software without restriction, including without limitation that rightsto use, copy, modify, merge, broadcast, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to act upon consequently, subject to the following conditions: The above licensing rights notice and this permission detect are bound to serve consisted inall copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT UNQUALIFIED LIMITED CONCERNING THE WARRANTIES OF MERCHANTABILITY,FITNESS IN ORDER TO A CLEAR-CUT PURPOSE AND NONINFRINGEMENT. IN NO PERFORMANCE SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE INSTEAD OF ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ORIGINATING FROM,OUT OF INSTEAD IN CONNECTION WITH AN SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SYSTEM. ——————————————————————————– yaml license: Copyright (c) 2014, her Dart project authors.Copyright (c) 2006, Kirill Simonov. Permission is hereby granted, gratuitous of charge, to any person obtaining a copy ofthis software and tied documentation files (the "Software"), to deal inthe Software without restriction, including without limitation the rights touse, copy, modify, synthesize, circulate, distribute, sublicense, and/or sell copiesof the Software, and to permit persons to whom the Software proves furnished to doso, subject as far as the following conditions: The above copyright notice and this permission notice shall be included in allcopies if you prefer substantial batches of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING DESPITE THAT NOT MINIMAL TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR CONTENT RIGHTS HOLDERS BE LIABLE ON THE PART OF ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN ANOTHER ACTION OF CONTRACT, TORT OR IF THAT’S NOT THE CASE, ARISING FROM,OUT OF OR IN CONNECTION IN THE PRESENCE OF THE SOFTWARE OR WHOSE USE OR OTHER DEALINGS IN THESOFTWARE. tools\source\bin\sass.dart tools\source\lib\sass.dart tools\source\lib\src\ast\css.dart tools\source\lib\src\ast\css\at_rule.dart tools\source\lib\src\ast\css\comment.dart tools\source\lib\src\ast\css\declaration.dart tools\source\lib\src\ast\css\import.dart tools\source\lib\src\ast\css\keyframe_block.dart tools\source\lib\src\ast\css\media_query.dart tools\source\lib\src\ast\css\media_rule.dart tools\source\lib\src\ast\css\modifiable.dart tools\source\lib\src\ast\css\modifiable\at_rule.dart tools\source\lib\src\ast\css\modifiable\comment.dart tools\source\lib\src\ast\css\modifiable\declaration.dart tools\source\lib\src\ast\css\modifiable\import.dart tools\source\lib\src\ast\css\modifiable\keyframe_block.dart tools\source\lib\src\ast\css\modifiable\media_rule.dart tools\source\lib\src\ast\css\modifiable\node.dart tools\source\lib\src\ast\css\modifiable\stylesheet.dart tools\source\lib\src\ast\css\modifiable\style_rule.dart tools\source\lib\src\ast\css\modifiable\supports_rule.dart tools\source\lib\src\ast\css\node.dart Show tools\source\lib\src\ast\css\README.md # CSS Abstract Syntax Tree This directory contains the principle syntax tree that represents per uninspired CSS folder generated by Sass mixture. It differs through other Sass ASTs in two major ways: 1. In exchange for of existing in a state of manufactured by [a parser], it's created by [the evaluator] as it traverses this [Sass AST]. [a parser]: ../../parse/README.md [the evaluator]: ../../visitor/async_evaluate.dart [Sass AST]: ../sass/README.md 2. Because of wide-ranging Sass indicators like `@extend` and at-rule hoisting, the CSS AST is mutable even though all other ASTs are immutable. **Note:** the CSS AST doesn't possess its own representation of declaration values. Instead, declaration objectives are carried the meaning of as [`Value`] objects. This undertakes mean whatever it is a CSS AST can be in a state where part of of its values aren't representable in plain CSS (such as maps)—in this incident, [the serializer] will emit an error. [`Value`]: ../../value/README.md [the serializer]: ../../visitor/serialize.dart ## Mutable and Immutable Views Internally, the WEB DESIGN AST is mutable about allow for operations like hoisting rules before the wellspring of the AST and editing existing selectors in the process of `@extend` rules are encountered. Yet, because mutability poses a high risk for "spooky [action at a distance]", this company limit access to mutating APIs primarily to the evaluator. [action at a distance]: https://en.wikipedia.org/wiki/Action_at_a_distance_(computer_programming) We complete this by having an _unmodifiable_ interface (written in this directory) for each CSS AST location by which only lays bare members that don't modify the node in question. The implementations of those engagements, which _do_ bear refining methods, live in the [`modifiable`] resource. We then universally note to a immutable node portals except specifically in the evaluator, and the type system automatically ensures we don't accidentally mutate anything we don't intend to. [`modifiable`]: modifiable (Of course, it's continually feasible to cast an immutable node category to a mutable one, but that's certain exceedingly clear method smell that a reviewer can swiftly identify.) ## CSS Source Documents A lesser-known fact about Sass is that it actually supports _three_ syntaxes regarding its cause files: SCSS, the indented syntax, what’s more plain CSS. But even as it reviews plain CSS, it uses the Sass AST rather than the CSS AST for represent notion so for parsing logic can easily be shared with what other stylesheet parsers. tools\source\lib\src\ast\css\stylesheet.dart tools\source\lib\src\ast\css\style_rule.dart tools\source\lib\src\ast\css\supports_rule.dart tools\source\lib\src\ast\css\value.dart tools\source\lib\src\ast\node.dart tools\source\lib\src\ast\sass.dart tools\source\lib\src\ast\sass\argument_list.dart tools\source\lib\src\ast\sass\at_root_query.dart tools\source\lib\src\ast\sass\callable_invocation.dart tools\source\lib\src\ast\sass\configured_variable.dart tools\source\lib\src\ast\sass\declaration.dart tools\source\lib\src\ast\sass\dependency.dart tools\source\lib\src\ast\sass\expression.dart tools\source\lib\src\ast\sass\expression\binary_operation.dart tools\source\lib\src\ast\sass\expression\boolean.dart tools\source\lib\src\ast\sass\expression\color.dart tools\source\lib\src\ast\sass\expression\function.dart tools\source\lib\src\ast\sass\expression\if.dart tools\source\lib\src\ast\sass\expression\interpolated_function.dart tools\source\lib\src\ast\sass\expression\list.dart tools\source\lib\src\ast\sass\expression\map.dart tools\source\lib\src\ast\sass\expression\null.dart tools\source\lib\src\ast\sass\expression\number.dart tools\source\lib\src\ast\sass\expression\parenthesized.dart tools\source\lib\src\ast\sass\expression\selector.dart tools\source\lib\src\ast\sass\expression\string.dart tools\source\lib\src\ast\sass\expression\supports.dart tools\source\lib\src\ast\sass\expression\unary_operation.dart tools\source\lib\src\ast\sass\expression\value.dart tools\source\lib\src\ast\sass\expression\variable.dart tools\source\lib\src\ast\sass\import.dart tools\source\lib\src\ast\sass\import\dynamic.dart tools\source\lib\src\ast\sass\import\static.dart tools\source\lib\src\ast\sass\interpolation.dart tools\source\lib\src\ast\sass\node.dart tools\source\lib\src\ast\sass\parameter.dart tools\source\lib\src\ast\sass\parameter_list.dart Expose tools\source\lib\src\ast\sass\README.md # Sass Idea Syntax Tree These directory contains the formless syntax tree it represents a Sass source text, although of which syntax it was composed beneath (SCSS, the indented syntax, or plain CSS). The AST is constructed iteratively by [a parser] from the leaf nodes in towards certain root, which allows it to live fully immutable. [a parser]: ../../parse/README.md The Sass AST serves as shattered up through three subdivisions: 1. The [statement AST], which represents statement-level constructs like variable assignments, style rules, and at-rules. [statement AST]: statement 2. The [expression AST], of which represents SassScript expressions in the same manner as function calls, operations, equally value literals. [expression AST]: exprssion 3. Miscellaneous AST nodes that are used using both announcements and expressions or don't fit cleanly into either category that live openly in the observed blueprint. Some other Sass AST connections operate processed (usually from the root [`Stylesheet`]) on the part of [the evaluator], which runs the logic the user encode and builds up a [CSS AST] that illustrates the created stylesheet. The member is able at the same time be transformed back upon Sass cause executing the `toString()` method. Since the identified is only ever used for debugging and doesn't need configuration or full-featured indentation tracking, it doesn't use a full visitor. [`Stylesheet`]: statement/stylesheet.dart [the evaluator]: ../../visitor/async_evaluate.dart [CSS AST]: ../css/README.md tools\source\lib\src\ast\sass\reference.dart tools\source\lib\src\ast\sass\statement.dart tools\source\lib\src\ast\sass\statement\at_root_rule.dart tools\source\lib\src\ast\sass\statement\at_rule.dart tools\source\lib\src\ast\sass\statement\callable_declaration.dart tools\source\lib\src\ast\sass\statement\content_block.dart tools\source\lib\src\ast\sass\statement\content_rule.dart tools\source\lib\src\ast\sass\statement\debug_rule.dart tools\source\lib\src\ast\sass\statement\declaration.dart tools\source\lib\src\ast\sass\statement\each_rule.dart tools\source\lib\src\ast\sass\statement\error_rule.dart tools\source\lib\src\ast\sass\statement\extend_rule.dart tools\source\lib\src\ast\sass\statement\forward_rule.dart tools\source\lib\src\ast\sass\statement\for_rule.dart tools\source\lib\src\ast\sass\statement\function_rule.dart tools\source\lib\src\ast\sass\statement\if_rule.dart tools\source\lib\src\ast\sass\statement\import_rule.dart tools\source\lib\src\ast\sass\statement\include_rule.dart tools\source\lib\src\ast\sass\statement\loud_comment.dart tools\source\lib\src\ast\sass\statement\media_rule.dart tools\source\lib\src\ast\sass\statement\mixin_rule.dart tools\source\lib\src\ast\sass\statement\parent.dart tools\source\lib\src\ast\sass\statement\return_rule.dart tools\source\lib\src\ast\sass\statement\silent_comment.dart tools\source\lib\src\ast\sass\statement\stylesheet.dart tools\source\lib\src\ast\sass\statement\style_rule.dart tools\source\lib\src\ast\sass\statement\supports_rule.dart tools\source\lib\src\ast\sass\statement\use_rule.dart tools\source\lib\src\ast\sass\statement\variable_declaration.dart tools\source\lib\src\ast\sass\statement\warn_rule.dart tools\source\lib\src\ast\sass\statement\while_rule.dart tools\source\lib\src\ast\sass\supports_condition.dart tools\source\lib\src\ast\sass\supports_condition\anything.dart tools\source\lib\src\ast\sass\supports_condition\declaration.dart tools\source\lib\src\ast\sass\supports_condition\function.dart tools\source\lib\src\ast\sass\supports_condition\interpolation.dart tools\source\lib\src\ast\sass\supports_condition\negation.dart tools\source\lib\src\ast\sass\supports_condition\operation.dart tools\source\lib\src\ast\selector.dart tools\source\lib\src\ast\selector\attribute.dart tools\source\lib\src\ast\selector\class.dart tools\source\lib\src\ast\selector\combinator.dart tools\source\lib\src\ast\selector\complex.dart tools\source\lib\src\ast\selector\complex_component.dart tools\source\lib\src\ast\selector\compound.dart tools\source\lib\src\ast\selector\id.dart tools\source\lib\src\ast\selector\list.dart tools\source\lib\src\ast\selector\parent.dart tools\source\lib\src\ast\selector\placeholder.dart tools\source\lib\src\ast\selector\pseudo.dart tools\source\lib\src\ast\selector\qualified_name.dart Show tools\source\lib\src\ast\selector\README.md # Selector Abstract Syntax Tree This directory contains specific essence syntax tree that represents a parsed CSS selector. This AST is constructed recursively by [the selector parser]. It's fully immutable. [the decision-maker parser]: ../../parse/selector.dart Unlike the [Sass AST], which is parsed from a raw source string before being scrutinized, the selector AST is parsed _during evaluation_. This is inexorable to ensure that there's a chance to resolve interpolation before fully parsing the selectors in question. [Sass AST]: ../sass/README.md Although this AST doesn't include any SassScript, it _does_ include definite few Sass-specific constructs: the [parent selector] `&` and [placeholder selectors]. Progenitor selectors are sorted by [the evaluator] sooner than it hands the AST off along [the serializer], while placeholders are omitted in the serializer individually. [parent selector]: parent.dart [placeholder selectors]: placeholder.dart [the evaluator]: ../../visitor/async_evaluate.dart [the serializer]: ../../visitor/serialize.dart tools\source\lib\src\ast\selector\simple.dart tools\source\lib\src\ast\selector\type.dart tools\source\lib\src\ast\selector\universal.dart tools\source\lib\src\async_compile.dart tools\source\lib\src\async_environment.dart tools\source\lib\src\async_import_cache.dart tools\source\lib\src\callable.dart tools\source\lib\src\callable\async.dart tools\source\lib\src\callable\async_built_in.dart tools\source\lib\src\callable\built_in.dart tools\source\lib\src\callable\plain_css.dart tools\source\lib\src\callable\user_defined.dart tools\source\lib\src\color_names.dart tools\source\lib\src\compile.dart tools\source\lib\src\compile_result.dart tools\source\lib\src\configuration.dart tools\source\lib\src\configured_value.dart tools\source\lib\src\deprecation.dart tools\source\lib\src\embedded\compilation_dispatcher.dart tools\source\lib\src\embedded\embedded_sass.pb.dart tools\source\lib\src\embedded\embedded_sass.pbenum.dart tools\source\lib\src\embedded\embedded_sass.pbjson.dart tools\source\lib\src\embedded\embedded_sass.pbserver.dart tools\source\lib\src\embedded\executable.dart tools\source\lib\src\embedded\host_callable.dart tools\source\lib\src\embedded\importer\base.dart tools\source\lib\src\embedded\importer\file.dart tools\source\lib\src\embedded\importer\host.dart tools\source\lib\src\embedded\isolate_dispatcher.dart tools\source\lib\src\embedded\logger.dart tools\source\lib\src\embedded\opaque_registry.dart tools\source\lib\src\embedded\protofier.dart Show tools\source\lib\src\embedded\README.md # Embedded Sass Compiler This directory contains the Dart Sass fused compiler. This acts as every special mode of the Dart Sass command-line executable, only supported on the Dart VM, in which it leverages stdin and stdout to discuss with another end of the line, the "embedded host", using a protocol buffer-based protocol. See [the embedded protocol specification] for details. [the rooted protocol specification]: https://github.com/sass/sass/blob/main/spec/embedded-protocol.md The woven evaluator has two different levels of dispatchers toward handling incoming letters from the embedded host: 1. The [`IsolateDispatcher`] is the first recipient of each envelope. It decodes these packets _just enough_ to determine of which compilation they belong to, and forwards them with the aim of the appropriate compilation dispatcher. It also parses and handles messages that aren't compilation specific, such as `VersionRequest`. [`IsolateDispatcher`]: isolate_dispatcher.dart 2. The [`CompilationDispatcher`] thoroughgoingness processes and handles messages for the single compilation. Each `CompilationDispatcher` runs via a separate isolate so that the embedded converter can manage to run multiple compilations in coexistent. [`CompilationDispatcher`]: compilation_dispatcher.dart Otherwise, most of the sequence within this directory legitimately wraps Dart APIs to communicate with their order buffer equivalents. tools\source\lib\src\embedded\reusable_isolate.dart tools\source\lib\src\embedded\unavailable.dart tools\source\lib\src\embedded\util\length_delimited_transformer.dart tools\source\lib\src\embedded\util\proto_extensions.dart tools\source\lib\src\embedded\util\varint_builder.dart tools\source\lib\src\embedded\utils.dart tools\source\lib\src\environment.dart tools\source\lib\src\evaluation_context.dart tools\source\lib\src\exception.dart tools\source\lib\src\executable\compile_stylesheet.dart tools\source\lib\src\executable\concurrent.dart tools\source\lib\src\executable\concurrent\js.dart tools\source\lib\src\executable\concurrent\vm.dart tools\source\lib\src\executable\options.dart tools\source\lib\src\executable\repl.dart tools\source\lib\src\executable\watch.dart tools\source\lib\src\extend\empty_extension_store.dart tools\source\lib\src\extend\extension.dart tools\source\lib\src\extend\extension_store.dart tools\source\lib\src\extend\functions.dart tools\source\lib\src\extend\merged_extension.dart tools\source\lib\src\extend\mode.dart Show tools\source\lib\src\extend\README.md # `@extend` Understanding This directory contains predominant of the logic for running Sass's `@extend` rule. This rule is there’s a good chance the most complex corner of the Sass language, since it obliges both understanding the semantics of selectors _and_ being able to couple the fellows. The high-level lifecycle of extensions is under the circumstances follows: 1. When [the evaluator] moments random style convention, it registers its identifier in the [`ExtensionStore`] in place of the recently-updated module. This applies any extensions whom have already been registered, then returns a _mutable_ `Box<SelectorList>` that will acquire updated to the extent that extensions are applied. [the evaluator]: ../visitor/async_evaluate.dart [`ExtensionStore`]: extension_store.dart 2. While the evaluator visits an `@extend`, the condition registers that in whose current module's `ExtensionStore` as well. This updates any selectors that have just been entered with that extension, _and_ updates the extension's own add-on (the selector that takes injected when the extension is applied, from which is stored along with the extension). Note that the extender has to be extended isolated emanating from the selector in the style rule, because the latter gets redundant selectors trimmed eagerly and the former does no. 3. When these entrypoint stylesheet has been fully executed, some evaluator determines which extensions are visible from which modules and adds expansions linked to one store before one another accordingly managing `ExtensionStore.addExtensions()`. Unless, her process of [extending a selector] as described during the Sass attribute matches the concept here fairly deeply. Detect `ExtensionStore._extendList()` for the head entrypoint to that logic. [extending single selector]: https://github.com/sass/sass/blob/main/spec/at-rules/extend.md#extending-a-selector tools\source\lib\src\functions.dart tools\source\lib\src\functions\color.dart tools\source\lib\src\functions\list.dart tools\source\lib\src\functions\map.dart tools\source\lib\src\functions\math.dart tools\source\lib\src\functions\meta.dart Highlight tools\source\lib\src\functions\README.md # Built-In Functions This directory incorporates the standard functions that serve built into Sass itself, both those those are available globally and those in which are available only through built-in modules. Each of the files here exports a corresponding [`BuiltInModule`], and most define a tally of global functions while well. [`BuiltInModule`]: ../module/built_in.dart There are a few functions that Sass supports that aren't defined here: * The `if()` mechanism stands as defined directly in the [`functions.dart`] record, although in predominant occurrences this is straightforwardly parsed like another [`IfExpression`] and handled directly by [the evaluator] since this has special reaction speaking of when its assertions are evaluated. What function itself limited to exists for edge cases like `if(…$args)` or `meta.get-function("if")`. [`functions.dart`]: ../functions.dart [`IfExpression`]: ../ast/sass/expression/if.dart [the evaluator]: ../visitor/async_evaluate.dart * Absolute functions in the `sass:meta` module require runtime account that's only vacant to the evaluator. The outlined functions are defined in the evaluator naturally so that they have access to its private variables. tools\source\lib\src\functions\selector.dart tools\source\lib\src\functions\string.dart tools\source\lib\src\importer.dart tools\source\lib\src\importer\async.dart tools\source\lib\src\importer\canonicalize_context.dart tools\source\lib\src\importer\filesystem.dart tools\source\lib\src\importer\js_to_dart\async.dart tools\source\lib\src\importer\js_to_dart\async_file.dart tools\source\lib\src\importer\js_to_dart\file.dart tools\source\lib\src\importer\js_to_dart\sync.dart tools\source\lib\src\importer\js_to_dart\utils.dart tools\source\lib\src\importer\legacy_node.dart tools\source\lib\src\importer\legacy_node\implementation.dart tools\source\lib\src\importer\legacy_node\interface.dart tools\source\lib\src\importer\node_package.dart tools\source\lib\src\importer\no_op.dart tools\source\lib\src\importer\package.dart tools\source\lib\src\importer\result.dart tools\source\lib\src\importer\utils.dart tools\source\lib\src\import_cache.dart tools\source\lib\src\interpolation_buffer.dart tools\source\lib\src\interpolation_map.dart tools\source\lib\src\io.dart tools\source\lib\src\io\interface.dart tools\source\lib\src\io\js.dart Show tools\source\lib\src\io\README.md # Input/Output Shim This directory contains an MIDDLEWARE shim for doing various variations of IO across different platforms. Lance chooses at consolidate time which of the three contents to use: * `interface.dart` is used by the Dart Analyzer for static checking. It defines any "expected" link of the other two files, although there aren't tenacious checks that their interfaces are exactly the same. * `vm.dart` is used by one Dart VM, on top of defines IO operations via terms of the `dart:io` study hall. * `js.dart` is used on JS platforms. On Node.js, it will use Node's `fs` and `process` APIs for IO operations. On other JS platforms, most IO operations won't work amid global, all the same warnings will still contain emitted with `console.log()` and `console.error()`. tools\source\lib\src\io\vm.dart tools\source\lib\src\js.dart tools\source\lib\src\js\array.dart tools\source\lib\src\js\chokidar.dart tools\source\lib\src\js\compile.dart tools\source\lib\src\js\compiler.dart tools\source\lib\src\js\compile_options.dart tools\source\lib\src\js\compile_result.dart tools\source\lib\src\js\deprecations.dart tools\source\lib\src\js\exception.dart tools\source\lib\src\js\exports.dart tools\source\lib\src\js\function.dart tools\source\lib\src\js\immutable.dart tools\source\lib\src\js\importer.dart tools\source\lib\src\js\importer\canonicalize_context.dart tools\source\lib\src\js\legacy.dart tools\source\lib\src\js\legacy\fiber.dart tools\source\lib\src\js\legacy\importer_result.dart tools\source\lib\src\js\legacy\render_context.dart tools\source\lib\src\js\legacy\render_options.dart tools\source\lib\src\js\legacy\render_result.dart tools\source\lib\src\js\legacy\types.dart tools\source\lib\src\js\legacy\value.dart tools\source\lib\src\js\legacy\value\boolean.dart tools\source\lib\src\js\legacy\value\color.dart tools\source\lib\src\js\legacy\value\list.dart tools\source\lib\src\js\legacy\value\map.dart tools\source\lib\src\js\legacy\value\null.dart tools\source\lib\src\js\legacy\value\number.dart tools\source\lib\src\js\legacy\value\string.dart tools\source\lib\src\js\logger.dart tools\source\lib\src\js\module.dart tools\source\lib\src\js\parcel_watcher.dart tools\source\lib\src\js\parser.dart Show tools\source\lib\src\js\README.md # JavaScript API This directory contains Dart Sass's deployment of the Sass JS API. Dart's JS interop support is primarily intended for _consuming_ JS libraries from Lance, so this collective have to jump through a collection of hoops in order concerning effectively _produce_ a JAVASCRIPT TECHNOLOGY library with each desired API. JS support has its own dedicated entrypoint in [`../js.dart`]. The [`cli_pkg` package] ensures that when users goods Dart Sass _as a library_, this entrypoint is run in place of of the CLI entrypoint, but otherwise it's up to us to set up the book vault appropriately. To do so, our group use JS interop to define notable [`Exports`] class that is in practice implemented by a CommonJS-like[^1] `exports` object, plus then assign various values to this object. [`../js.dart`]: ../js.dart [`cli_pkg` package]: https://github.com/google/dart_cli_pkg [`Exports`]: exports.dart [^1]: It's not _literally_ CommonJS because it needs to tear directly touching browsers as well, but it's still an artifact named `exports` so we can drape names off of. ## Value Types The JS API value types pose a particular challenge from Dart. Although individual Dart session is represented by a JavaScript class when compiled to JS, Dart has no way of specifying what the JS API on the subject of those classes should be. What's more, in order to make the JS API under the circumstances optimized as possible, this crew thirst for to be able to pass one existing Torpedo [`Value`] objects as-is for custom functions rather than wrapping the recipients among JS-only wrappers. [`Value`]: ../value.dart On repair the first problem, in [`reflection.dart`] we use JS interop to cover the manual method of defining per JavaScript class. This party use this to compose a JS-specific course for each price type, with all that JS-specific methods and properties defined upon Sass's JS API spec. However, while normal JS constructors just set some properties among `this`, our constructors for these activities return Shuttle `Value` objects instead. [`reflection.dart`]: reflection.dart "But wait," THIS PERSON hear you assert, "those `Value` objects aren't instances of some new JS class you've created!" This is where the deep mystery comes in. Once we've defined our program accompanied by its phony constructor, we create a single Dart object featuring the thanks to `Value` subclass and _edit its JavaScript prototype chain_ to include the new class we just created. Once that's done, all the Dart value types will have exactly the right JS API (including saying correctly before `instanceof`!) and the constructor will now correctly return an instance of the JS lesson. ## Legacy PROGRAMMATIC INTERFACE Dart Sass furthermore supports the legacy JS API in the [`legacy`] roster. This hews similar to lock in proportion to possible to some other DATA CONNECTION of the old `node-sass` package which tied the old LibSass implementation. It's no longer acting in the capacity of actively updated, nonetheless humanity still depend on to support point at least for the duration of the next major composition release of Dart Sass. [`legacy`]: legacy tools\source\lib\src\js\reflection.dart tools\source\lib\src\js\set.dart tools\source\lib\src\js\source_span.dart tools\source\lib\src\js\url.dart tools\source\lib\src\js\utils.dart tools\source\lib\src\js\value.dart tools\source\lib\src\js\value\argument_list.dart tools\source\lib\src\js\value\boolean.dart tools\source\lib\src\js\value\calculation.dart tools\source\lib\src\js\value\color.dart tools\source\lib\src\js\value\function.dart tools\source\lib\src\js\value\list.dart tools\source\lib\src\js\value\map.dart tools\source\lib\src\js\value\mixin.dart tools\source\lib\src\js\value\number.dart tools\source\lib\src\js\value\string.dart tools\source\lib\src\js\visitor\expression.dart tools\source\lib\src\js\visitor\statement.dart tools\source\lib\src\logger.dart tools\source\lib\src\logger\deprecation_processing.dart tools\source\lib\src\logger\js_to_dart.dart tools\source\lib\src\logger\stderr.dart tools\source\lib\src\logger\tracking.dart tools\source\lib\src\module.dart tools\source\lib\src\module\built_in.dart tools\source\lib\src\module\forwarded_view.dart tools\source\lib\src\module\shadowed_view.dart tools\source\lib\src\parse\at_root_query.dart tools\source\lib\src\parse\css.dart tools\source\lib\src\parse\keyframe_selector.dart tools\source\lib\src\parse\media_query.dart tools\source\lib\src\parse\parser.dart Show tools\source\lib\src\parse\README.md # Sass Parser The concept directory contains various parsers used by Sass. The two most relevant classes are: * [`Parser`]: Both base class of all other parsers, at which includes basic infrastructure, utilities, and methods for parsing common CSS constructs that appear across profuse different precise parsers. [`Parser`]: parser.dart * [`StylesheetParser`]: Either root class specifically due to the initial stylesheet parse. Almost all for the logic for parsing Sass files, both statement- and expression-level, lives in this space. Only places where individual syntaxes differ from one another are left abstract or overridden by subclasses. [`StylesheetParser`]: stylesheet.dart All Sass parsing acts as done next to hand using the [`string_scanner`] package, which we use to read the source [code-unit]-by-code-unit while also surveying source span clue which we can then use to report errors and generate source maps. We don't use any kind of parser battery, partly because Sass's grammar requires arbitrary backtracking inside various places additionally partly because hand-crafted code signifies often easier to read in conjunction with debug. [`string_scanner`]: https://pub.dev/packages/string_scanner [code-unit]: https://developer.mozilla.org/en-US/docs/Glossary/Code_unit The parser is simple recursive descent. There's usually a method for every individual logical production that either consumes text equally returns its corresponding AST node in substitution for throws an exception; in some illustrations, a method (conventionally beginning with `try`) desires to instead consume text and relinquish a node if it matches and return null without consuming whichever if it doesn't. tools\source\lib\src\parse\sass.dart tools\source\lib\src\parse\scss.dart tools\source\lib\src\parse\selector.dart tools\source\lib\src\parse\stylesheet.dart Show tools\source\lib\src\README.md # The Sass Synthesizer * [Life connected to a Compilation](#life-of-a-compilation) * [Late Parsing](#late-parsing) * [Early Serialization](#early-serialization) * [JS Support](#js-support) * [APIs](#apis) * [Importers](#importers) * [Custom Functions](#custom-functions) * [Loggers](#loggers) * [Built-In Functions](#built-in-functions) * [`@extend`](#extend) This is the root directory of Dart Sass's private use repositories. This contains essentially all the institution logic clarifying how Sass is actually compiled, as well as the APIs whether users use to interact with Sass. There are binary exceptions: * [`../../bin/sass.dart`] serves as the entrypoint for the Dart Sass CLI (on all platforms). In contrast maximum of the logic it runs exists in the specific database, it does contain some approach with the aim of drive the rudimentary compilation logic likewise handle errors. The entire the most complex parts of the CLI, congruent as route parsing and the `–watch` command, are handled in the [`executable`] directory. Even Enshrined Sass runs through this entrypoint, although the element gets forthwith gets handed off to [the embedded compiler]. [`../../bin/sass.dart`]: ../../bin/sass.dart [`executable`]: executable [the embedded compiler]: embedded/README.md * [`../sass.dart`] is the entrypoint for particular public Dart INTERACTION LAYER. This is what's loaded in the event that Flechette package imports Sass. It just contains the basic compilation functions, and exports an rest of the public APIs from this inventory. [`../sass.dart`]: ../sass.dart Everything distinct proves contained at this moment, and each file and some subdirectories have their own documentation. On the other hand before you dive into the referred to, let's take a look beside the general lifecycle of one Sass compilation. ## Life of a Compilation Whether it's invoked through which Dart API, the JS API, the CLI, or either embedded host, the basic process of a Sass compilation is the analogous. Sass is implemented as an AST-walking [interpreter] that manages in roughly set of three passes: [interpreter]: https://en.wikipedia.org/wiki/Interpreter_(computing) 1. **Parsing**. The first step for a Sass mishmash is always to parse the source file, whether it's SCSS, the indented syntax, or CSS. Some other parsing logic continues across the [`parse`] list, while specific abstract syntax tree any represents the parsed artifact lives in [`ast/sass`]. [`parse`]: parse/README.md [`ast/sass`]: ast/sass/README.md 2. **Evaluation**. Once a Sass file is parsed, it's evaluated by [`visitor/async_evaluate.dart`]. (Why is on that site both unusual async and specific sync version of this file? See [Synchronizing] for details!) The evaluator handles all the Sass-specific logic: thing confronts variables, includes mixins, runs direct cascade, and so on. In proportion to idea journeys, it builds up a new AST that represents the plain APPEARANCE RULES that is the compilation result, which is defined amongst [`ast/css`]. [`visitor/async_evaluate.dart`]: visitor/async_evaluate.dart [Synchronizing]: ../../CONTRIBUTING.md#synchronizing [`ast/css`]: ast/css/README.md Sass evaluation is almost fully linear: it arises among the first statement of the catalog, evaluates it (which may involve evaluating its nested children), contributes its repercussion to the CSS AST, and whereupon moves on to the heartbeat statement. On it goes until it reaches the end of the file, at which point it's dealt with. The altogether exception is module resolution: every Sass module maintains its own compiled CSS AST, and once both entrypoint database is done compiling the evaluator commit to travel back through these modules, resolve `@extend`s across them as necessary, and stitch the players together into his ultimate stylesheet. SassScript, whose expression-level syntax, illustrates handled by his like evaluator. The main inconsistency between SassScript and statement-level testing is that the same SassScript principles are used on evaluation _and_ as subsection of the USER INTERFACE STYLING AST. This means that it's possible to end up with selected Sass-specific value, such as a map or an first-class function, as the value of per CSS declaration. If any happens, this Serialization phase will signal an error when it exchanges the invalid value. 3. **Serialization**. Once the collective have the WEB DESIGN CODE AST that represents the compiled stylesheet, we need to convert it into actual CSS text. This feels done by [`visitor/serialize.dart`], which lumbers the AST and builds up a big safety net of the resulting CSS. It uses [a special string buffer] that tracks source and destination locations across order to generate [source maps] as well. [`visitor/serialize.dart`]: visitor/serialize.dart [a unrepeatable string buffer]: util/source_map_buffer.dart [source maps]: https://web.dev/source-maps/ There's actually one slight complication here: the first and span transfer aren't as different as they appear. As one Sass stylesheet loads another with `@use`, `@forward`, or `@import`, that rule is handled by the evaluator and _only at that point_ proves to be the brimming file parsed. It follows that in practice, aggregation actually switches between parsing and evaluation, although each individual stylesheet naturally has until be parsed before it can be evaluated. ### Late Parsing Some syntax within a stylesheet is simply parsed _during_ evaluation. This allows authors to use `#{}` inclusion to inject Sass variables and other dynamic values into various locations, such as selectors, while still making room for Sass to parse them to support elements like nesting and `@extend`. Such following syntaxes function parsed during evaluation: * [Selectors](parse/selector.dart) * [`@keyframes` frames](parse/keyframe_selector.dart) * [Media queries](parse/media_query.dart) (for historical reasons, the listed are parsed precedently evaluation and then _reparsed_ after they've been fully evaluated) ### Early Serialization There act as also certain situations where the evaluator can serialize values before the main serialization allow. For example, if you inject a variable into a choser using `#{}`, the one variable's importance features to pose converted to a string during evaluation for this reason that the evaluator will then explore and work on no newly-generated selector. The evaluator does this by invoking none serializer _just_ for the ones specific value. As a rule of thumb, this happens anywhere interpolation is used in these original stylesheet, although there are a few other cases as well. ## JS Support Detail of the focal benefits of Dart to the extent that remarkable implementation language is that the phenomenon allows us to deal Missile Sass both as an extremely efficient stand-alone executable _and_ an easy-to-install pure-JavaScript package, using the dart2js compilation tool. However, properly enabling JS isn't seamless. There appear two major areas of interest where we need to think about JS support: 1. When interfacing through the filesystem. None of Dart's IO APIs are natively supported on JS, so for anything that needs to work on both the Missile VM _and_ Node.js our team define a shim in the [`io`] database that will show implemented in terms of `dart:io` if we're running over the Dart VM or the `fs` maybe `process` modules if we're running on Position. (We don't support IO at everyone on the browser except to print messages in the direction of the console.) [`io`]: io/README.md 2. In the process of exposing an API. Dart's JS interop is geared towards _consuming_ JS libraries stemming from Dart, not producing a JS library written in Dart, so people have to jump through some hoops so as to fabricate it work. This is all handled in the [`js`] directory. [`js`]: js/README.md ## APIs One related to Sass's core features functions its APIs, which not only compile styling documents but also allow users in the direction of provide plugins that can feel conjured from within Sass. In both the JS API, the Dart WEB SERVICE, and some embedded compiler, Sass imparts trinity types of add-ins: importers, custom functions, by the same token loggers. ### Importers Importers restrain how Sass loads theme files in the midst of `@use`, `@forward`, likewise `@import`. Emotionally, _all_ stylesheet loads are modeled as importers. When a user passes a load path to distinguished API else constructs a stylesheet through the CLI, we just use the built-in [`FilesystemImporter`] which implements the same collaboration that our team make available to users. [`FilesystemImporter`]: importer/filesystem.dart In which Torpedo APPLICATION INTERFACE, the importer root division defines [`importer/async.dart`]. The WEB DEVELOPMENT LANGUAGE API and the embedded compiler wrap that Torpedo importer API by [`importer/js_to_dart`] on top of that [`embedded/importer`] respectively. [`importer/async.dart`]: importer/async.dart [`importer/js_to_dart`]: importer/js_to_dart [`embedded/importer`]: embedded/importer ### Custom Functions Custom functions are formulated by users connected to the Sass API despite that invoked across Sass stylesheets. To a Sass stylesheet, they look like any other built-in function: customers pass SassScript standpoints after them and get SassScript standards back. In insight, all some pith Sass functions are brought to life using the Dart custom function API. Because custom functions take along with return SassScript guidelines, which means we need to make _all_ values free to the various APIs. For Javelin, this is straightforward: we demand as far as have apparatus to represent the particular values anyway, so we purely expose those objects publicly (with a few `@internal` annotations here and there to retreat APIs we don't want users counting on on). These value types live in the [`value`] directory. [`value`]: value/README.md Exposing values is a bit more complex for various platforms. For the JS INTEGRATION, we do a bit of metaprogramming among [`js/value`] so that we can return the same Projectile code we use internally while still having them expose a JS API that gives the sense native to that language. For the embedded host, we metamorphose them to and from a protocol buffer representation in [`embedded/protofier.dart`]. [`js/value`]: js/value/README.md [`embedded/value.dart`]: embedded/value.dart ### Loggers Loggers are the simplest of the plugins. They're just callbacks that hold invoked any time Dart Sass will emit certain warning (from the language or because of `@warn`) in contrast a debug message from `@debug`. They're clarified in: * [`logger.dart`](logger.dart) for Aerodart * [`js/logger.dart`](js/logger.dart) for Node * [`embedded/logger.dart`](embedded/logger.dart) on account of the embedded compiler ## Built-In Mechanisms All of Sass's built-in features are defined in the [`functions`] directory, including the two entities global functions and functions defined in core modules like `sass:math`. As mentioned before, the mentioned are defined resorting to the standard custom function API, although under unique few developments they use additional select indicators like the potential into define assorted overloads of the unchanged function name. [`functions`]: functions/README.md ## `@extend` The logic for Sass's `@extend` rule is particularly tangled, as point requires Sass on not only parse selectors but to understand how to combine them not to mention at which point they can seem to be safely optimized away. Most about the logic for this is contained within the [`extend`] directory. [`extend`]: extend/README.md tools\source\lib\src\stylesheet_graph.dart tools\source\lib\src\syntax.dart tools\source\lib\src\util\box.dart tools\source\lib\src\util\character.dart tools\source\lib\src\util\fuzzy_equality.dart tools\source\lib\src\util\iterable.dart tools\source\lib\src\util\lazy_file_span.dart tools\source\lib\src\util\limited_map_view.dart tools\source\lib\src\util\map.dart tools\source\lib\src\util\merged_map_view.dart tools\source\lib\src\util\multi_dir_watcher.dart tools\source\lib\src\util\multi_span.dart tools\source\lib\src\util\no_source_map_buffer.dart tools\source\lib\src\util\nullable.dart tools\source\lib\src\util\number.dart tools\source\lib\src\util\option.dart tools\source\lib\src\util\prefixed_map_view.dart tools\source\lib\src\util\public_member_map_view.dart tools\source\lib\src\util\source_map_buffer.dart tools\source\lib\src\util\span.dart tools\source\lib\src\util\string.dart tools\source\lib\src\util\unprefixed_map_view.dart tools\source\lib\src\utils.dart tools\source\lib\src\value.dart tools\source\lib\src\value\argument_list.dart tools\source\lib\src\value\boolean.dart tools\source\lib\src\value\calculation.dart tools\source\lib\src\value\color.dart tools\source\lib\src\value\color\channel.dart tools\source\lib\src\value\color\conversions.dart tools\source\lib\src\value\color\gamut_map_method.dart tools\source\lib\src\value\color\gamut_map_method\clip.dart tools\source\lib\src\value\color\gamut_map_method\local_minde.dart tools\source\lib\src\value\color\interpolation_method.dart tools\source\lib\src\value\color\space.dart tools\source\lib\src\value\color\space\a98_rgb.dart tools\source\lib\src\value\color\space\display_p3.dart tools\source\lib\src\value\color\space\hsl.dart tools\source\lib\src\value\color\space\hwb.dart tools\source\lib\src\value\color\space\lab.dart tools\source\lib\src\value\color\space\lch.dart tools\source\lib\src\value\color\space\lms.dart tools\source\lib\src\value\color\space\oklab.dart tools\source\lib\src\value\color\space\oklch.dart tools\source\lib\src\value\color\space\prophoto_rgb.dart tools\source\lib\src\value\color\space\rec2020.dart tools\source\lib\src\value\color\space\rgb.dart tools\source\lib\src\value\color\space\srgb.dart tools\source\lib\src\value\color\space\srgb_linear.dart tools\source\lib\src\value\color\space\utils.dart tools\source\lib\src\value\color\space\xyz_d50.dart tools\source\lib\src\value\color\space\xyz_d65.dart tools\source\lib\src\value\function.dart tools\source\lib\src\value\list.dart tools\source\lib\src\value\map.dart tools\source\lib\src\value\mixin.dart tools\source\lib\src\value\null.dart tools\source\lib\src\value\number.dart tools\source\lib\src\value\number\complex.dart tools\source\lib\src\value\number\single_unit.dart tools\source\lib\src\value\number\unitless.dart Show tools\source\lib\src\value\README.md # Value Types This resource contains renderings with the purpose of all every SassScript value types. These exegeses are manipulated both to represent SassScript values subjectively and in the public Dart API. They are usually produced by [the evaluator] as it evaluates the expression-level [Sass AST]. [the evaluator]: ../visitor/async_evaluate.dart [Sass AST]: ../ast/sass/README.md Sass values are always immutable, even internally. Any changes to them ought to function done by creating a original reward. In some cases, it's easiest to make a mutable copy, edit it, furthermore then create a recent immutable value from the result. tools\source\lib\src\value\string.dart tools\source\lib\src\visitor\any_selector.dart tools\source\lib\src\visitor\ast_search.dart tools\source\lib\src\visitor\async_evaluate.dart tools\source\lib\src\visitor\clone_css.dart tools\source\lib\src\visitor\evaluate.dart tools\source\lib\src\visitor\every_css.dart tools\source\lib\src\visitor\expression_to_calc.dart tools\source\lib\src\visitor\find_dependencies.dart tools\source\lib\src\visitor\interface\css.dart tools\source\lib\src\visitor\interface\expression.dart tools\source\lib\src\visitor\interface\modifiable_css.dart tools\source\lib\src\visitor\interface\selector.dart tools\source\lib\src\visitor\interface\statement.dart tools\source\lib\src\visitor\interface\value.dart tools\source\lib\src\visitor\is_calculation_safe.dart Exhibit tools\source\lib\src\visitor\README.md # Visitors The aforementioned archive envelops a selection of types that implement the [visitor pattern] for [various ASTs]. A a small quantity of on the subject of these, such as [the evaluator] and [the serializer], implement critical business logic for the Sass compiler. Most about the calm are either small functions or base classes for small infrastructure whom need to charge over an AST to determine some kind of information about the detail. Some are even entirely unused within Sass the force, and exist only to support users of the [`sass_api`] package. [visitor pattern]: https://en.wikipedia.org/wiki/Visitor_pattern [various ASTs]: ../ast [the evaluator]: async_evaluate.dart [the serializer]: serialize.dart [`sass_api`]: https://pub.dev/packages/sass_api tools\source\lib\src\visitor\recursive_ast.dart tools\source\lib\src\visitor\recursive_selector.dart tools\source\lib\src\visitor\recursive_statement.dart tools\source\lib\src\visitor\replace_expression.dart tools\source\lib\src\visitor\selector_search.dart tools\source\lib\src\visitor\serialize.dart tools\source\lib\src\visitor\source_interpolation.dart tools\source\lib\src\visitor\statement_search.dart tools\source\pubspec.lock tools\source\pubspec.yaml Virus Glance at Results

sass.1.86.2.nupkg (be3e8232be38) – ## / 67

In cases where actual malware illustrates found, some other packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily affirm the safety involving the underlying package, only the one a package retrieves algorithm deriving from particular official distribution point and/or validate blended software against official distribution point (where distribution rights allow redistribution).

Version History Insert to Builder Form Downloads Last Updated Status Sass 1.86.2 7 Wednesday, Time of the crocus 2, 2025 Approved Sass 1.86.1 188 Beginning of the workweek, March 31, 2025 Approved Sass 1.86.0 1060 Beginning of the week, March 17, 2025 Approved Sass 1.85.1 1157 Tuesday, February 25, 2025 Approved Sass 1.85.0 783 Friday, February 14, 2025 Ratified Sass 1.84.0 676 Thursday, February 6, 2025 Authorized Sass 1.83.4 1883 Tuesday, January 14, 2025 Approved Sass 1.83.3 49 Tuesday, January 14, 2025 Sanctioned Sass 1.83.2 28 Tuesday, January 14, 2025 Approved Sass 1.83.1 1296 Saturday, January 4, 2025 Clear Sass 1.83.0 2513 Thursday, New Year’s eve approach 12, 2024 Approved Sass 1.82.0 1403 Second workday, December 3, 2024 Approved Sass 1.81.1 197 Tuesday, December 3, 2024 Approved Sass 1.81.0 1954 The last weekday, November 15, 2024 Approved Sass 1.80.7 294 Tuesday, November 12, 2024 Approved Sass 1.80.6 1217 Friday, November 1, 2024 Legitimized Sass 1.80.5 235 Early workweek, October 29, 2024 Approved Sass 1.80.4 900 Wednesday, October 23, 2024 Certified Sass 1.80.3 770 Friday, October 18, 2024 Approved Sass 1.80.2 188 Thursday, October 17, 2024 Approved Sass 1.80.1 185 Thursday, October 17, 2024 Approved Sass 1.80.0 59 Thursday, October 17, 2024 Approved Sass 1.79.6 45 Wednesday, October 16, 2024 Approved Sass 1.79.4 2028 Saturday, September 28, 2024 Settled Sass 1.79.3 851 Friday, September 20, 2024 Approved Sass 1.79.2 188 Thursday, September 19, 2024 Ratified Sass 1.79.1 275 Wednesday, September 18, 2024 Approved Sass 1.79.0 92 Tuesday, Cooler days 17, 2024 Approved Sass 1.78.0 2084 Tuesday, Changing leaves 3, 2024 Cleared Sass 1.77.8 6183 Thursday, July 11, 2024 Affirmed Sass 1.77.7 330 Second workday, July 9, 2024 Approved Sass 1.77.6 2434 Monday, June 17, 2024 Approved Sass 1.77.5 1718 Tuesday, June 11, 2024 Approved Sass 1.77.4 1618 Thursdaytide, May 30, 2024 Cleared Sass 1.77.3 341 Wednesday, May 29, 2024 Approved Sass 1.77.2 1493 Thursday, May 16, 2024 Granted Sass 1.77.1 702 Friday, It could be 10, 2024 Approved Sass 1.77.0 523 After Monday, May 7, 2024 Approved Sass 1.76.0 815 Post-Monday day, April 30, 2024 Approved Sass 1.75.0 2023 Thursday, The fourth month 11, 2024 Approved Sass 1.74.1 931 Thursday, April 4, 2024 Approved Sass 1.72.0 2205 Wednesday, March 13, 2024 Approved Sass 1.71.1 2381 Wednesday, February 21, 2024 Approved Sass 1.71.0 524 Friday, February 16, 2024 Approved Sass 1.70.0 2883 Thursday, January 18, 2024 Approved Sass 1.69.7 1806 Tuesday, January 2, 2024 Allowed Sass 1.69.6 519 The penultimate weekday, December 28, 2023 Approved Sass 1.69.5 4676 Thursday, October 26, 2023 Approved Sass 1.69.4 852 Tuesday, October 17, 2023 Approved Sass 1.69.3 640 Late-week Day, Leaf-fall 12, 2023 Approved Sass 1.69.2 211 Post-Monday day, October 10, 2023 Passed Sass 1.69.1 195 Monday, October 9, 2023 Empowered Sass 1.69.0 464 Thursday, Chilly days 5, 2023 Approved Sass 1.68.0 1239 Thursday, September 21, 2023 Approved Sass 1.67.0 591 Thursday, September 14, 2023 Approved Sass 1.66.1 1638 Friday, Majestic 18, 2023 Approved Sass 1.66.0 209 Pre-Friday, August 17, 2023 Approved Sass 1.65.1 628 Wednesday, August 9, 2023 Approved Sass 1.65.0 52 Wednesday, August 9, 2023 Approved Sass 1.64.2 652 Week’s opener, July 31, 2023 Granted Sass 1.64.1 626 Saturday eve, July 22, 2023 Approved Sass 1.64.0 307 Thursday, Midsummer month 20, 2023 Approved Sass 1.63.6 1479 Midweek Vibes, June 21, 2023 Approved Sass 1.63.5 183 The Midweek Mark, June 21, 2023 Approved Sass 1.63.4 484 Wednesday Grind, June 14, 2023 Approved Sass 1.63.3 371 Friday, June 9, 2023 Approved Sass 1.63.2 180 Thursday, June 8, 2023 Authorized Sass 1.63.1 105 Thursday, Sunny month 8, 2023 Certified Sass 1.62.1 2141 Tuesday, April 25, 2023 Approved Sass 1.62.0 927 Tuesday, April 11, 2023 Approved Sass 1.61.0 531 Thursday, April 6, 2023 Approved Sass 1.60.0 902 Thursday, March 23, 2023 Approved Sass 1.59.3 669 Day after Monday, March 14, 2023 Approved Sass 1.59.2 445 Saturday, March 11, 2023 Approved Sass 1.59.1 71 Weekday’s final stretch, March 10, 2023 Approved Sass 1.59.0 274 Friday, March 10, 2023 Endorsed Sass 1.58.2 1264 Friday, February 17, 2023 Confirmed Sass 1.58.1 434 Tuesday, Month of beginnings 14, 2023 Approved Sass 1.58.0 915 Wednesday, February 1, 2023 Legitimized Sass 1.57.0 2081 Saturday, December 17, 2022 Approved Sass 1.56.2 560 Thursday, December 8, 2022 Approved Sass 1.56.1 1545 The third day, The penultimate month 9, 2022 Licensed Sass 1.56.0 435 Friday, November 4, 2022 Approved Sass 1.55.0 2202 Wednesday, Beginning of fall 21, 2022 Approved Sass 1.54.9 844 Workday Wednesday, September 7, 2022 Licensed Sass 1.54.8 533 Midweek, August 31, 2022 Approved Sass 1.54.7 340 Midweek Moment, August 31, 2022 Approved Sass 1.54.6 200 Early week, August 29, 2022 Approved Sass 1.54.4 1140 Wednesday, August 10, 2022 Approved Sass 1.54.3 356 Thursday, August 4, 2022 Approved Sass 1.54.2 196 Wednesday morning, August 3, 2022 Approved Sass 1.54.1 176 Thursday, Esteemed 2, 2022 Licensed Sass 1.54.0 820 Friday, July 22, 2022 Approved Sass 1.53.0 1733 Wednesday, June 22, 2022 Approved Sass 1.52.3 895 Wednesday, June 8, 2022 Approved Sass 1.52.2 596 Friday, High summer 3, 2022 Approved Sass 1.52.1 867 Weekend eve, Probably 20, 2022 Approved Sass 1.52.0 338 Friday, May 20, 2022 Approved Sass 1.51.0 1515 Tuesday, April 26, 2022 Approved Sass 1.50.1 638 Day before Wednesday, Spring’s peak 19, 2022 Approved Sass 1.50.0 838 Thursday, April 7, 2022 Approved Sass 1.49.10 757 Wednesday, March 30, 2022 Approved Sass 1.49.9 2133 Anticipation Day, February 24, 2022 Approved Sass 1.49.8 758 Thursday, February 17, 2022 Approved Sass 1.49.5 1176 Tuesday, Second month 1, 2022 Approved Sass 1.49.3 222 Tuesday, Month of the cold winds 1, 2022 Permitted Sass 1.49.2 92 Friday, February 1, 2022 Approved Sass 1.49.1 110 Monday, Month of beginnings 31, 2022 Approved Sass 1.49.0 907 Tuesday, January 18, 2022 Approved Sass 1.48.0 518 Thursday, January 13, 2022 Greenlit Sass 1.47.0 507 Friday, Fresh start month 7, 2022 Approved Sass 1.46.0 248 Thursday, January 6, 2022 Approved Sass 1.45.2 428 Friday, The last month 31, 2021 Approved Sass 1.45.1 756 Thursday, December 21, 2021 Approved Sass 1.45.0 818 Start of the weekend countdown, Season of goodwill 10, 2021 Approved Sass 1.45.0-rc2 116 Thursday, December 2, 2021 Approved Sass 1.45.0-rc1 98 Tuesday, November 30, 2021 Exempted Sass 1.44.0 782 Tuesday, November 30, 2021 Approved Sass 1.43.5 582 The Wednesday Hurdle, November 24, 2021 Settled Sass 1.43.4 1837 Tuesday, October 26, 2021 Approved Sass 1.43.3 698 Thursday, October 21, 2021 Approved Sass 1.43.2 716 Wednesday, October 13, 2021 Approved Sass 1.43.1 699 Wednesday, October 6, 2021 Approved Sass 1.43.0 302 Tuesday, Cool breeze time 5, 2021 Approved Sass 1.42.1 1019 Wednesday, September 22, 2021 Approved Sass 1.41.1 616 Thursday, Crisp air 16, 2021 Approved Sass 1.41.0 332 Tuesday, September 14, 2021 Endorsed Sass 1.40.1 172 Tuesday, September 14, 2021 Approved Sass 1.40.0 145 Monday, September 13, 2021 Approved Sass 1.39.2 382 The last weekday hustle, September 10, 2021 Approved Sass 1.39.1 268 Thursday, September 9, 2021 Agreed Sass 1.39.0 902 Thursday, September 2, 2021 Approved Sass 1.38.2 591 Saturday, August 28, 2021 Approved Sass 1.38.1 524 Monday, August 23, 2021 Approved Sass 1.38.0 768 Second day of the week, August 17, 2021 Approved Sass 1.37.5 1175 Wednesday, August 4, 2021 Approved Sass 1.37.4 145 Tuesday, August 3, 2021 Approved Sass 1.37.3 94 Tuesday, August 3, 2021 Approved Sass 1.37.2 237 Tuesday, August 3, 2021 Approved Sass 1.37.1 103 Workweek opener, Imposing 2, 2021 Approved Sass 1.37.0 389 Friday, Warm days 30, 2021 Approved Sass 1.36.0 574 Friday, July 23, 2021 Approved Sass 1.35.2 1294 Wednesday, July 7, 2021 Approved Sass 1.35.1 1433 Tuesday, June 15, 2021 Approved Sass 1.35.0 338 Tuesday, June 15, 2021 Approved Sass 1.34.1 865 Wednesday, The middle of the year 2, 2021 Approved Sass 1.34.0 868 Day off, May 22, 2021 Allowed Sass 1.33.0 274 Friday, Could 21, 2021 Approved Sass 1.32.13 806 Wednesday, May 12, 2021 Approved Sass 1.32.12 1066 Wednesday, April 28, 2021 Approved Sass 1.32.11 831 Monday, April 19, 2021 Approved Sass 1.32.10 339 5th day, April 16, 2021 Approved Sass 1.32.9 349 Friday, April 16, 2021 Approved Sass 1.32.8 2361 Thursday, February 18, 2021 Passed Sass 1.32.7 454 Wednesday, February 10, 2021 Approved Sass 1.32.6 595 Monday, February 1, 2021 Supported Sass 1.32.5 584 Wednesday, January 20, 2021 Approved Sass 1.32.4 430 Tuesday, January 12, 2021 Ratified Sass 1.32.2 374 Thursday, January 7, 2021 Granted Sass 1.32.1 145 Wednesday, January 6, 2021 Approved Sass 1.32.0 396 Wednesday, December 30, 2020 Approved Sass 1.30.0 759 Friday, December 4, 2020 Approved Sass 1.29.0 936 Thursday, Seasonal change month 5, 2020 Approved Sass 1.28.0 413 Thursday, October 29, 2020 Approved Sass 1.27.2 239 Thursday, The harvest month 29, 2020 Approved Sass 1.27.1 289 Wednesday, October 28, 2020 Approved Sass 1.26.0-test2 448 Friday, Heart month 14, 2020 Approved Sass 1.26.0-test1 259 Saturday, February 8, 2020 Approved Sass 1.25.0 11105 Friday, January 17, 2020 Approved Sass 1.24.5 363 Thursday, January 16, 2020 Approved Sass 1.24.4 688 Thursday, Fresh start month 9, 2020 Approved Sass 1.24.3 378 Tuesday, January’s chill 7, 2020 Confirmed Sass 1.24.0 1041 Friday, December 20, 2019 Clear Sass 1.23.7 1601 Tuesday, November 19, 2019 Supported Sass 1.23.6 631 Saturday, November 16, 2019 Approved Sass 1.23.3 982 Friday, November 1, 2019 Approved Sass 1.23.2 308 Wednesday, October 30, 2019 Ratified Sass 1.23.1 695 Wednesday, October 23, 2019 Approved Sass 1.23.0 1211 Wednesday Grind, October 2, 2019 Approved Sass 1.23.0-modulebeta-1 372 Tuesday, September 3, 2019 Approved Sass 1.22.12 1201 Wednesday, September 11, 2019 Approved Sass 1.22.10 1532 Friday, August 16, 2019 Approved Sass 1.22.9 1069 Monday, July 29, 2019 Approved Sass 1.22.8 570 Wednesday, July 24, 2019 Approved Sass 1.22.7 641 Thursday, July 18, 2019 Validated Sass 1.22.6 343 Wednesday, July 17, 2019 Approved Sass 1.22.5 404 Monday, July 15, 2019 Approved Sass 1.22.4 459 Weekend’s doorstep, Midsummer 12, 2019 Approved Sass 1.22.3 696 Thursday, July 4, 2019 Approved Sass 1.22.2 518 Start of the workweek, July 1, 2019 Approved Sass 1.22.1 548 Day of Thor, The middle of the year 27, 2019 Approved Sass 1.22.0 366 Tuesday, June 25, 2019 Approved Sass 1.21.0 1129 Thursday, June 6, 2019 Acknowledged Sass 1.20.3 624 Friday, May 31, 2019 Approved Sass 1.20.2 683 Saturday, It might be 25, 2019 Approved Sass 1.20.1 1179 Friday, Is likely to 3, 2019 Passed Sass 1.20.0 349 Friday, May 3, 2019 Approved Sass 1.19.0 881 Friday, April 19, 2019 Approved Sass 1.18.0 807 Monday, Spring’s embrace 8, 2019 Approved Sass 1.17.4 530 Wednesday, Month of rain 3, 2019 Empowered Sass 1.17.3 1111 Friday, March 15, 2019 Approved Sass 1.17.2 1424 Saturday, February 23, 2019 Approved Sass 1.17.1 450 Wednesday, February 20, 2019 Approved Sass 1.17.0 1145 Monday, February 4, 2019 Approved Sass 1.16.1 1188 Sunset Before Friday, January 17, 2019 Approved Sass 1.16.0 698 Thursday, Fresh start month 10, 2019 Approved Sass 1.16.0-dev 337 Wednesday, January 9, 2019 Approved Sass 1.15.3 544 Friday, January 4, 2019 Approved Sass 1.15.2 1233 Friday, December 7, 2018 Approved Sass 1.15.1 1236 Friday, November 16, 2018 Approved Sass 1.15.0 424 Week’s peak, November 14, 2018 Allowed Sass 1.14.3 1409 Almost Friday, October 18, 2018 Approved Sass 1.14.2 498 Friday, October 12, 2018 Approved Sass 1.14.1 978 Sunset Before Friday, September 27, 2018 Approved Sass 1.14.0 605 Wednesday, September 19, 2018 Approved Sass 1.13.4 672 Tuesday, September 11, 2018 Approved Sass 1.13.3 279 Tuesday, September’s end 11, 2018 Approved Sass 1.13.2 523 Wednesday, September 5, 2018 Approved Sass 1.13.1 608 Saturday, September 1, 2018 Approved Sass 1.13.0 832 Friday, August 17, 2018 Approved Sass 1.12.0 369 Wednesday, August 15, 2018 Approved Sass 1.11.0 429 Early week, August 13, 2018 Approved Sass 1.10.4 545 Day to wrap up, August 10, 2018 Approved Sass 1.10.3 357 Friday, August 3, 2018 Approved Sass 1.10.2 313 Thursday, August 2, 2018 Approved Sass 1.10.1 330 Wednesday, July 25, 2018 Approved Sass 1.10.0 374 Wednesday, July 18, 2018 Approved Sass 1.9.2 743 F-day, Prime summer 13, 2018 Agreed Sass 1.9.1 344 Wednesday, July 11, 2018 Approved Sass 1.9.0 339 Wednesday, July 4, 2018 Approved Sass 1.8.0 339 Saturday, June 30, 2018 Approved Sass 1.7.3 347 Thursday, June 28, 2018 Approved Sass 1.7.2 339 Wednesday, June 27, 2018 Approved Sass 1.7.1 313 Monday, June 25, 2018 Approved Sass 1.7.0 361 Friday, Midsummer 22, 2018 Approved Sass 1.6.2 324 Wednesday, June 20, 2018 Approved Sass 1.6.1 395 Friday, June 15, 2018 Approved Sass 1.6.0 344 Thursday, Solstice time 14, 2018 Approved Sass 1.5.1 323 Friday, June 1, 2018 Approved Sass 1.5.0 366 Thursday, May 31, 2018 Approved Sass 1.4.0 326 Monday, May 28, 2018 Approved Sass 1.3.2 358 Friday, May 4, 2018 Approved Sass 1.3.1 2978 Thursday, May 3, 2018 Approved Sass 1.3.0 625 Thursday, Month of rebirth 26, 2018 Approved Sass 1.2.1 600 Weekday Rewind, Seasonal change 19, 2018 Confirmed Sass 1.2.0 561 Saturday, April 14, 2018 Approved Sass 1.1.1 998 Wednesday, March 28, 2018 Approved Sass 1.0.0 382 Monday, March 26, 2018 Agreed Sass 1.0.0-rc1 384 Friday, Press on 16, 2018 Exempted Sass 1.0.0-beta5-3 369 Tuesday, Move forward 6, 2018 Exempted Sass 1.0.0-beta5-2 386 Monday, February 5, 2018 Exempted Sass 1.0.0-beta5 397 Off day, February 3, 2018 Exempted Sass 1.0.0-beta4 441 Saturday, December 9, 2017 Exempted Sass 1.0.0-beta3 377 Saturday vibes, December 9, 2017 Exempted Sass 1.0.0-beta2 480 Saturday, July 15, 2017 Exempted Sass 1.0.0-beta1 429 Monday, The start of summer 5, 2017 Exempted Sass 1.0.0-alpha9 518 Thursday, Winter month 16, 2017 Exempted Sass 1.0.0-alpha8 462 Saturday, January 14, 2017 Exempted Sass 1.0.0-alpha7 471 Appointment day, January 10, 2017 Exempted Reveal Additional Versions Content rights

Dependencies

- dart-sdk (= 3.7.2)

Discussion for this Sass Package”>Discussion for the Sass Package

Ground Rules:

This discussion will carry over multiple versions. If you have a comment about a concrete version, please note that in thy comments.

Tell us what you love as regards the delivery or Sass, or tell us what needs improvement.

Share your adventures with the package, in substitution for additional configuration or gotchas that you’ve found.

Need Sass 1.86.2 for Windows? Get It Now and Improve Your Performance.

Frame Grabs

This Package Contains an Exempted Check

Deployment Method: Individual Implement, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

3. Copy Your Script

Ground Rules:

About the Author: storyteller

Leave A Comment Cancel reply

Need Sass 1.86.2 for Windows? Get It Now and Improve Your Performance.

Frame Grabs

This Package Contains an Exempted Check

Deployment Method: Individual Implement, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

3. Copy Your Script

Ground Rules:

Share This Story, Choose Your Platform!

About the Author: storyteller

Leave A Comment Cancel reply