svg-symbol-sprite-loader Update: dependencies 🆙 (major)

Update: dependencies 🆙 (major)

Open renovate[bot] opened this issue 3 years ago • 0 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ionicons (source)	`5.5.1` -> `7.2.2`
parse5	`6` -> `7`
react (source)	`17.0.2` -> `18.2.0`
react-dom (source)	`17.0.2` -> `18.2.0`
webpack-sources	`2` -> `3`

Release Notes

ionic-team/ionicons (ionicons)

`v7.2.2`

Compare Source

Bug Fixes

icon: add better warning when loading icons (#1297) (d582e62)

`v7.2.1`

Compare Source

Bug Fixes

icon: font scales without host style (#1289) (875bfd8)

`v7.2.0`

Compare Source

Bug Fixes

icon: mapping same icon does not warn (#1279) (8297018)
icon: verify the icon loads in the lifecycle (#1278) (7f7f346)

Features

allow passing in only icon SVG data to addIcons (#1256) (1e33313)
icon: support for dynamic type (#1246) (45c04dd)

7.1.2 (2023-05-30)

Bug Fixes

icon: add :dir fallback (#1223) (06fa4a5)

7.1.1 (2023-05-23)

Bug Fixes

icon: respond to changes of document dir (#1210) (e70bf21)

`v7.1.2`

Compare Source

Bug Fixes

icon: add :dir fallback (#1223) (06fa4a5)

`v7.1.1`

Compare Source

Bug Fixes

icon: respond to changes of document dir (#1210) (e70bf21)

`v7.1.0`

Compare Source

Features

chevron-expand and chevron-collapse icons (#1198) (cdb0d80)

Migration Note: Developers should ensure that their <ion-icon> usages have either aria-label or aria-hidden to avoid accessibility issues. See https://ionic.io/ionicons/usage for more information.

Bug Fixes

icon: remove auto-generated aria-label (#1170) (98975ec)

6.1.3 (2023-02-09)

Bug Fixes

DomParser usage in SSR (#1180) (8c412f6), closes #1179

6.1.2 (2023-02-08)

Bug Fixes

icon: load base64 data urls (#1172) (72f0936)
icon: md and ios properties are reactive (#1174) (65bcbb4), closes #802

6.1.1 (2023-01-18)

Bug Fixes

icon: remove during build step (<a href="https://togithub.com/ionic-team/ionicons/issues/1169" rel="nofollow" target="_blank" >#1169</a>) (<a href="https://togithub.com/ionic-team/ionicons/commit/93b4fa449b0a072b24ef920fe73e1cb04d6f9b43" rel="nofollow" target="_blank" >93b4fa4</a>), closes <a href="https://togithub.com/ionic-team/ionicons/issues/1168" rel="nofollow" target="_blank" >#1168</a>

6.1.1 (2023-01-18)

Bug Fixes

icon: remove during build step (<a href="https://togithub.com/ionic-team/ionicons/issues/1169" rel="nofollow" target="_blank" >#1169</a>) (<a href="https://togithub.com/ionic-team/ionicons/commit/93b4fa449b0a072b24ef920fe73e1cb04d6f9b43" rel="nofollow" target="_blank" >93b4fa4</a>), closes <a href="https://togithub.com/ionic-team/ionicons/issues/1168" rel="nofollow" target="_blank" >#1168</a>

`v6.1.3`

Compare Source

Bug Fixes

DomParser usage in SSR (#1180) (8c412f6), closes #1179

`v6.1.2`

Compare Source

Bug Fixes

icon: load base64 data urls (#1172) (72f0936)
icon: md and ios properties are reactive (#1174) (65bcbb4), closes #802

`v6.1.1`

Compare Source

Bug Fixes

icon: remove during build step (<a href="https://togithub.com/ionic-team/ionicons/issues/1169" rel="nofollow" target="_blank" >#1169</a>) (<a href="https://togithub.com/ionic-team/ionicons/commit/93b4fa449b0a072b24ef920fe73e1cb04d6f9b43" rel="nofollow" target="_blank" >93b4fa4</a>), closes <a href="https://togithub.com/ionic-team/ionicons/issues/1168" rel="nofollow" target="_blank" >#1168</a>

`v6.1.0`

Compare Source

Bug Fixes

icon: remove default (<a href="https://togithub.com/ionic-team/ionicons/issues/1166" rel="nofollow" target="_blank" >#1166</a>) (<a href="https://togithub.com/ionic-team/ionicons/commit/e0efa5f28d61adcaf2e1fa121f7e2f10cfad6d65" rel="nofollow" target="_blank" >e0efa5f</a>), closes <a href="https://togithub.com/ionic-team/ionicons/issues/838" rel="nofollow" target="_blank" >#838</a> <a href="https://togithub.com/ionic-team/ionicons/issues/1049" rel="nofollow" target="_blank" >#1049</a> <a href="https://togithub.com/ionic-team/ionicons/issues/1082" rel="nofollow" target="_blank" >#1082</a>

fix(icon): using icon in ssr environment no longer errors on HTMLElement (#1035) 3ec9271

`v6.0.0`

Compare Source

fix(icon): avoid type collisions with ariaLabel and ariaHidden (#1014) 1038a7f

BREAKING CHANGE:

The ariaLabel and ariaHidden properties have been removed in favor of using the aria-label and aria-hidden attributes. For most developers there will be no change in behavior. Please review the migration steps below to see if you need to update your application:

Using Ionicons via JavaScript:

// Before
iconEl.ariaHidden = "true";

// After
iconEl.setAttribute('aria-hidden', 'true');

Using Ionicons via JSX in React

{/* Before */}
<IonIcon ariaHidden="true" />

{/* After */}
<IonIcon aria-hidden="true" />

This change is more aligned with what React expects: https://reactjs.org/docs/accessibility.html#wai-aria

`v5.5.4`

Compare Source

fix(): build with stencil 2.10 (#1015) f21bb0f

`v5.5.3`

Compare Source

fix(): reflect name property as attribute (#981) e63653c

`v5.5.2`

Compare Source

fix(build): re-add legacy ionicons.js file (#982) 24caaad

inikulin/parse5 (parse5)

`v7.1.2`

Compare Source

This release includes parse5 and parse5-parser-stream.

Export ERR as ErrorCodes by @milahu in https://github.com/inikulin/parse5/pull/704
Properly handle CR when peeking by @fb55 in https://github.com/inikulin/parse5/pull/715
Add CJS build of parser-stream by @fb55 in https://github.com/inikulin/parse5/pull/716

Full Changelog: https://github.com/inikulin/parse5/compare/v7.1.0...v7.1.2

`v7.1.1`

Compare Source

`v7.1.0`

Compare Source

This release is only for the parse5 module.

What's Changed

feat(parse5): use string types for node names by @43081j in https://github.com/inikulin/parse5/pull/631
fix(parser): Have </button> close <p> by @fb55 in https://github.com/inikulin/parse5/pull/534
docs: Fix small typo in code example by @cheeaun in https://github.com/inikulin/parse5/pull/518
Added coverage reporting by @fb55 in https://github.com/inikulin/parse5/pull/515
Improved code coverage by @fb55 in https://github.com/inikulin/parse5/pull/517 and https://github.com/inikulin/parse5/pull/547

New Contributors

@cheeaun made their first contribution in https://github.com/inikulin/parse5/pull/518

Full Changelog: https://github.com/inikulin/parse5/compare/v7.0.0...v7.1.0

`v7.0.0`

Compare Source

Welcome to parse5@7.0.0! ✨ This is a huge release with many changes, features and fixes.

From an organisational perspective, the most important change is that parse5 is now maintained by a team, consisting of James (@43081j), Titus (@wooorm) and me (@fb55). We come from three projects that rely on parse5 — namely Cheerio, rehype, and Lit.

We need your support to continue the project! If you care about parse5, please support us financially on OpenCollective.

Headlining features of this release are ES Modules, TypeScript, and performance improvements: 7.0.0 is 45% faster than 6.0.1 with default options, and 167% faster with location information enabled (for the bench/perf benchmark, on an M1 Mac). Version 7.0.0 is a revamp of every part of the library. There are too many changes to list them all here, so here is a high-level overview:

Breaking: ESM

All of parse5’s packages are now ECMAScript Modules. We are providing dual packages for parse5 and parse5-htmlparser2-tree-adapter for now (see https://github.com/inikulin/parse5/pull/418 and https://github.com/inikulin/parse5/pull/496).

To migrate, please read this Gist on how to update. Note that private internals are no longer available; instead, everything that you need should be imported from the main package.

Implemented by @43081j in #351

Breaking: TypeScript

The codebase has been ported to TypeScript. This helped uncover a number of subtle logic bugs, such as dc4e269, b4b5d4a, or a0aff95. TypeScript also helps us refactor with confidence and a lot of the changes in this release would have been much harder to do without it.

To migrate, please remove @types/parse5* as we now ship our own types.

Implemented by @fb55 in #362

Potentially breaking changes

parse5 was caught up with the HTML spec, and parsing results might differ in edge-cases (https://github.com/inikulin/parse5/pull/442, https://github.com/inikulin/parse5/pull/451)
The parse5-serializer-stream package was removed https://github.com/inikulin/parse5/pull/481
- To migrate, use the serialize function exported by parse5.
The rewriting stream now splits very long text sections (https://github.com/inikulin/parse5/pull/434) and doesn’t escape text in special tags anymore (#434). If you worked around these issues before, you might have to update your code.
The htmlparser2 adapter now uses domhandler’s node interface (https://github.com/inikulin/parse5/pull/327 by @TrySound)
- The format of the tree nodes has changed slightly; eg. some previous properties are now getters and setters, and vice versa.

If you are using deep imports for any parts of the codebase, you will likely encounter some breakages:

Show internal changes

The tokenizer now uses the state machine pattern from htmlparser2 5d7a780 (#362)
The token queue was replaced with callbacks (https://github.com/inikulin/parse5/pull/404, https://github.com/inikulin/parse5/pull/405, https://github.com/inikulin/parse5/pull/419)
The OpenElementStack now uses callbacks https://github.com/inikulin/parse5/pull/429
Mixins were removed (as part of #362)
- Location tracking now has a substantially lower overhead https://github.com/inikulin/parse5/pull/402
getNextToken was removed https://github.com/inikulin/parse5/pull/461
The parser’s _bootstrap method was removed https://github.com/inikulin/parse5/pull/384
We now drop chunks from the tokenizer right after they are emitted https://github.com/inikulin/parse5/pull/432
The serializer is no longer a class; instead, different serializer functions call on each other https://github.com/inikulin/parse5/pull/383
parse5 now uses the entities module for encoding and decoding entities, sharing maintenance & optimisation work with projects such as htmlparser2 (2b92054 (#362), https://github.com/inikulin/parse5/pull/486)
- entities adopted a variant of parse5’s approach of decoding entities. As a result, decoding performance is equivalent, while memory consumption is slightly lower.

Other changes

minor add hooks for stack events to tree adapter interface #385
minor add support for fragments in parse5-parser-stream #487
minor add serializeOuter (like .outerHTML), scriptingEnabled option #383
patch fix parsing of << in comments parsed wrongly as <! (#326)
patch fix position of endTag for mixed-case foreign elements (#353)
patch fix end position of html, body (#436)
docs: parse5 has a new documentation website at parse5.js.org #443

New Contributors

Thanks @anko, @TrySound, @samouri, @alan-agius4, and @pmdartus!

Full Changelog: https://github.com/inikulin/parse5/compare/v6.0.1...v7.0.0

facebook/react (react)

`v18.2.0`

Compare Source

React DOM

Provide a component stack as a second argument to onRecoverableError. (@gnoff in #24591)
Fix hydrating into document causing a blank page on mismatch. (@gnoff in #24523)
Fix false positive hydration errors with Suspense. (@gnoff in #24480 and @acdlite in #24532)
Fix ignored setState in Safari when adding an iframe. (@gaearon in #24459)

React DOM Server

Pass information about server errors to the client. (@salazarm and @gnoff in #24551 and #24591)
Allow to provide a reason when aborting the HTML stream. (@gnoff in #24680)
Eliminate extraneous text separators in the HTML where possible. (@gnoff in #24630)
Disallow complex children inside <title> elements to match the browser constraints. (@gnoff in #24679)
Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@jplhomer in #24641)

Server Components (Experimental)

Add support for useId() inside Server Components. (@gnoff in #24172)

`v18.1.0`

Compare Source

React DOM

Fix the false positive warning about react-dom/client when using UMD bundle. (@alireza-molaee in #24274)
Fix suppressHydrationWarning to work in production too. (@gaearon in #24271)
Fix componentWillUnmount firing twice inside of Suspense. (@acdlite in #24308)
Fix some transition updates being ignored. (@acdlite in #24353)
Fix useDeferredValue causing an infinite loop when passed an unmemoized value. (@acdlite in #24247)
Fix throttling of revealing Suspense fallbacks. (@sunderls in #24253)
Fix an inconsistency in whether the props object is the same between renders. (@Andarist and @acdlite in #24421)
Fix a missing warning about a setState loop in useEffect. (@gaearon in #24298)
Fix a spurious hydration error. (@gnoff in #24404)
Warn when calling setState in useInsertionEffect. (@gaearon in #24295)
Ensure the reason for hydration errors is always displayed. (@gaearon in #24276)

React DOM Server

Fix escaping for the bootstrapScriptContent contents. (@gnoff in #24385)
Significantly improve performance of renderToPipeableStream. (@gnoff in #24291)

ESLint Plugin: React Hooks

Fix false positive errors with a large number of branches. (@scyron6 in #24287)
Don't consider a known dependency stable when the variable is reassigned. (@afzalsayed96 in #24343)

Use Subscription

Replace the implementation with the use-sync-external-store shim. (@gaearon in #24289)

`v18.0.0`

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes. Read React 18 release post and React 18 upgrade guide for more information.

New Features

React

useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.

React DOM Client

These new APIs are now exported from react-dom/client:

createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

renderToPipeableStream: for streaming in Node environments.
renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

webpack/webpack-sources (webpack-sources)

`v3.2.3`

Compare Source

`v3.2.2`

Compare Source

Bugfixes

Source Code is splitted into lines via custom code instead of using a RegExp
- In weird edge cases the RegExp caused a Stack Overflow

`v3.2.1`

Compare Source

Bugfixes

RawSources with Buffers can now be concatenated with ConcatSource
Source Code is splitted into lines via custom code instead of using a RegExp
- In weird edge cases the RegExp caused a Stack Overflow