- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1
fix(deps): update dependencies #86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Open
      
      
            renovate
  wants to merge
  1
  commit into
  main
  
    
      
        
          
  
    
      Choose a base branch
      
     
    
      
        
      
      
        
          
          
        
        
          
            
              
              
              
  
           
        
        
          
            
              
              
           
        
       
     
  
        
          
            
          
            
          
        
       
    
      
from
renovate/dependencies
  
      
      
   
  
    
  
  
  
 
  
      
    base: main
Could not load branches
            
              
  
    Branch not found: {{ refName }}
  
            
                
      Loading
              
            Could not load tags
            
            
              Nothing to show
            
              
  
            
                
      Loading
              
            Are you sure you want to change the base?
            Some commits from the old base branch may be removed from the timeline,
            and old review comments may become outdated.
          
          
                
     Open
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    ad564e2    to
    0ef5dd3      
    Compare
  
    0d26268    to
    eaf7737      
    Compare
  
    6b29849    to
    7d99d37      
    Compare
  
    b5a1d3c    to
    a1736f7      
    Compare
  
    3430511    to
    fa237a5      
    Compare
  
    64be2d9    to
    85050d5      
    Compare
  
    aa18696    to
    55e7fad      
    Compare
  
    64fdd7b    to
    a399a50      
    Compare
  
    91f4809    to
    f50e46f      
    Compare
  
    38b7fa5    to
    0b3f975      
    Compare
  
    0b3f975    to
    337a2fe      
    Compare
  
    337a2fe    to
    7e284d9      
    Compare
  
    7e284d9    to
    c3ef0d1      
    Compare
  
    c3ef0d1    to
    5eaca2e      
    Compare
  
    
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR contains the following updates:
7.0.6->7.1.22.1.1->2.1.58.5.3->8.5.60.16.6->0.16.75.0.1->5.0.2^3.3.2->^4.0.05.39.0->5.44.0Release Notes
cssnano/cssnano (cssnano)
v7.1.2: v7.1.2Compare Source
What's Changed
Full Changelog: https://github.com/cssnano/cssnano/compare/[email protected]@7.1.2
v7.1.1: v71.1.1Compare Source
Bug Fixes
linear()from stripping%from value 0 by @cernymatej in #1720Full Changelog: https://github.com/cssnano/cssnano/compare/[email protected]@7.1.1
v7.1.0Compare Source
Changes
v7.0.7Compare Source
What's Changed
Full Changelog: https://github.com/cssnano/cssnano/compare/[email protected]@7.0.7
posthtml/htmlnano (htmlnano)
v2.1.5Compare Source
Fixed
v2.1.4Compare Source
Fixed
v2.1.3Compare Source
Changed
docs/from the npm package.v2.1.2Compare Source
Added
skipInternalWarningsflag to avoidconsole.warnoutput [#293]Fixed
sortinstead oftimsort[#328]postcss/postcss (postcss)
v8.5.6Compare Source
ContainerWithChildrentype discriminating (by @Goodwine).v8.5.5Compare Source
package.json→exportscompatibility with some tools (by @JounQin).v8.5.4Compare Source
posthtml/posthtml (posthtml)
v0.16.7Compare Source
sindresorhus/srcset (srcset)
v5.0.2Compare Source
654e61560d80ecsvg/svgo (svgo)
v4.0.0Compare Source
Illustration by Vukory
It's been just over a year since our first release candidate, but I believe we can now release SVGO v4.0.0 with confidence! Thank you to all contributors who tested our RC builds and reported issues back up, this really smoothed out the process.
We actually wanted to do the release sooner, but it was a challenge to find the right time to publish a major release, since that means setting time aside to support users through migrations, helping downstream projects migrate, being available to fix or document things that users found to have an unexpected impact by this release, etc. I appreciate everyone's patience, and now that this is done, we can hopefully increase the pace of development again and tackle that backlog of old bugs. ^-^'
Breaking Changes
Please refer to the Migration Guide from v3 to v4 for a more concise version! This section is more verbose as it delves into the motivation of changes too.
Dropped Support for Node.js v14
Node.js v14 is no longer supported by the Node.js team, including security support, since 30 April 2023. Node.js v16 is no longer supported either, but as some are still using it, we'll save dropping support for Node.js v16 for the next major release.
This allows us to update our dependencies to more recent versions and to access more modern Node.js APIs.
Node.js v14 may still work at the time of this release, but we'll no longer be testing against v14 from now on.
Default Plugins
Both removeViewBox and removeTitle have been disabled by default. Both have been major pain points for users and don't make sense to enable in most cases. Other libraries wrapping SVGO have also been disabling these plugins by default, such as Docusaurus and SVGR.
If you would like either of these plugins enabled, you can do so by configuring it in the SVGO config, see the README for more context, however please read the warnings described in the documentation of the plugins first:
export default { plugins: [ 'preset-default', // built-in plugins enabled by default + 'removeViewBox', + 'removeTitle', ], };removeScriptElement → removeScripts
The removeScriptElement plugin has been renamed to removeScripts, to more accurately reflect what the plugin does. It does not only remove the
<script>tag, but also event handlers and script URIs from links.To migrate, amend your SVGO config to refer to
removeScriptsinstead if you use that plugin.export default { plugins: [ 'preset-default', // built-in plugins enabled by default - 'removeScriptElement', + 'removeScripts', ], };Imports/Exports
We now enforce boundaries between the intended public API and any internal structures/helpers. This is the biggest change in SVGO's JavaScript API and will enable maintainers and users to have a mutual understanding of what is public API and what isn't.
There are two ways to import SVGO:
svgo— for normal usage, such as scripts or server-side applications.svgo/browser— for browser usage.If you use the browser bundle, you must amend how you import SVGO:
For ESM/browser, you must use named imports:
We support 3 environments, ESM, Common JS, and browser. The only functional difference is that the
loadConfigfunction is not exported in the browser bundle.If you depended on a helper that we haven't declared as public, then you are encouraged to implement it yourself, or dig into our source and copy it over to your project.
Importing Plugins
If you import/require the array of built-in plugins, or a single plugin during runtime, this is now a top-level export instead:
Selector Helpers
The
XastNode#parentNodeproperty was declared legacy and pending removal for v4, but was still used internally. The remaining instances have now been removed, which required a refactor of the selector helpers.This effects custom plugins that use any of the following functions, where the
selector(2nd) argument could reference parent or sibling nodes (i.e.div > span):querySelectorAllquerySelectormatchesPreviously, these functions had the context of the whole node tree, even if a child node was passed to it. It no longer has that context by default. The new API for these functions is as follows:
A helper has been provided named
#mapNodesToParents, which does this for you. This can be used to easily migrate to the new API. If you're not sure if you need it, then it's safer to take this approach. The third argument won't be necessary ifselectordoes not traverse nodes, for example, querying using one or more attributes of a single node.What Else
ESM
SVGO is now a dual package, serving for both Common JS and ESM usage. To be more explicit, SVGO will continue to work on Common JS projects!
Thanks to @jdufresne for doing the bulk of the work.
Default Behavior
convertCasetofalse.Bug Fixes
filterattribute. By @johnkenny54 in #1933path[opacity=0]as a non-rendering node. By @johnkenny54 in #1948-oargument) ends with a trailing slash to a location that didn't exist. By @SethFalco in #1954Features
VERSIONexport so get the version of SVGO during runtime. By @SethFalco in #2016isPresetandpluginsproperty to plugins, which are only defined for presets. This will indicate if the plugin is a preset, and return the plugins that are in the preset in the order they are invoked.SVG Optimization
Performance
Developer Experience
Metrics
Before and after using vectors from various sources, with the default preset of each respective version:
Note: The increase in size from previous versions is from disabling
removeViewBoxandremoveTitle, with the benefit of preserving scalability and accessibility.Before and after of the browser bundle of each respective version:
terser/terser (terser)
v5.44.0Compare Source
usingandawait usingdeclarations (#1635)v5.43.1Compare Source
lhs_constantstoCompressOptionstype (#1621)v5.43.0Compare Source
wrap_func_argsformat option is now false by default)v5.42.0Compare Source
v5.41.0Compare Source
keep_numbersformat option now works for bigintv5.40.0Compare Source
export {}(#1601)constandletresulting from ESTree input (#1599)v5.39.2Compare Source
yieldinside a template string.v5.39.1Compare Source
BigIntandnumberConfiguration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.