jellyfin-web
jellyfin-web copied to clipboard
Update dependencies
This PR contains the following updates:
Release Notes
zloirock/core-js
v3.24.1
- NodeJS is ignored in
IS_BROWSER
detection to avoid a false positive withjsdom
, #1110 - Fixed detection of
@@​species
support inPromise
in some old engines -
{ Array, %TypedArray% }.prototype.{ findLast, findLastIndex }
marked as shipped in FF104 - Added iOS Safari 15.6 compat data mapping
- Fixed Opera 15 compat data mapping
v3.24.0
- Recent updates of the iterator helpers proposal, #1101:
-
.asIndexedPairs
renamed to.indexed
, proposal-iterator-helpers/183:-
Iterator.prototype.asIndexedPairs
->Iterator.prototype.indexed
-
AsyncIterator.prototype.asIndexedPairs
->AsyncIterator.prototype.indexed
-
- Avoid exposing spec fiction
%AsyncFromSyncIteratorPrototype%
inAsyncIterator.from
andIterator.prototype.toAsync
, proposal-iterator-helpers/182, proposal-iterator-helpers/202 - Avoid unnecessary promise creation in
%WrapForValidAsyncIteratorPrototype%.next
, proposal-iterator-helpers/197 - Do not validate value in
%WrapForValid(Async)IteratorPrototype%.next
, proposal-iterator-helpers/197 and proposal-iterator-helpers/205 - Do not forward the parameter of
.next
/.return
to an underlying iterator by the extended iterator protocol, a part of proposal-iterator-helpers/194 -
.throw
methods removed from all wrappers / helpers prototypes, a part of proposal-iterator-helpers/194 - Close inner iterators of
{ Iterator, AsyncIterator }.prototype.flatMap
proxy iterators on.return
, proposal-iterator-helpers/195 - Throw
RangeError
onNaN
in{ Iterator, AsyncIterator }.prototype.{ drop, take }
, proposal-iterator-helpers/181 - Many other updates and fixes of this proposal
-
-
%TypedArray%.prototype.toSpliced
method removed from the change array by copy proposal and marked as obsolete incore-js
, proposal-change-array-by-copy/88 - Polyfill
Promise
withunhandledrejection
event support (browser style) in Deno < 1.24 - Available new targets in
core-js-compat
/core-js-builder
and added compat data for them: - Added Samsung Internet 18.0 compat data mapping
v3.23.5
- Fixed a typo in the
structuredClone
feature detection, #1106 - Added Opera Android 70 compat data mapping
v3.23.4
- Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of
core-js
- Added a fix of the FF103+
structuredClone
bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but.stack
of the clone is an empty string - Fixed
{ Map, WeakMap }.prototype.emplace
logic, #1102 - Fixed order of errors throwing on iterator helpers
v3.23.3
- Changed the order of operations in
%TypedArray%.prototype.toSpliced
following proposal-change-array-by-copy/89 - Fixed regression of some IE8- issues
v3.23.2
- Avoided creation of extra properties for the handling of
%TypedArray%
constructors in new methods, #1092 (comment) - Added Deno 1.23 compat data mapping
v3.23.1
- Fixed possible error on multiple
core-js
copies, #1091 - Added
v
flag toRegExp.prototype.flags
implementation in case if current V8 bugs will not be fixed before this flag implementation
v3.23.0
-
Array
find from last moved to the stable ES, according to June 2022 TC39 meeting:-
Array.prototype.findLast
-
Array.prototype.findLastIndex
-
%TypedArray%.prototype.findLast
-
%TypedArray%.prototype.findLastIndex
-
- Methods from the
Array
grouping proposal renamed, according to June 2022 TC39 meeting:-
Array.prototype.groupBy
->Array.prototype.group
-
Array.prototype.groupByToMap
->Array.prototype.groupToMap
-
- Changed the order of operations in
%TypedArray%.prototype.with
following proposal-change-array-by-copy/86, according to June 2022 TC39 meeting -
Decorator Metadata proposal extracted from Decorators proposal as a separate stage 2 proposal, according to March 2022 TC39 meeting,
Symbol.metadataKey
replacesSymbol.metadata
- Added
Array.prototype.push
polyfill with some fixes for modern engines - Added
Array.prototype.unshift
polyfill with some fixes for modern engines - Fixed a bug in the order of getting flags in
RegExp.prototype.flags
in the actual version of V8 - Fixed property descriptors of some
Math
andNumber
constants - Added a workaround of V8
ArrayBufferDetaching
protector cell invalidation and performance degradation onstructuredClone
feature detection, one more case of #679 - Added detection of NodeJS bug in
structuredClone
that can not cloneDOMException
(just in case for future versions that will fix other issues) - Compat data:
- Added NodeJS 18.3 compat data mapping
- Added and fixed Deno 1.22 and 1.21 compat data mapping
- Added Opera Android 69 compat data mapping
- Updated Electron 20.0 compat data mapping
v3.22.8
- Fixed possible multiple call of
ToBigInt
/ToNumber
conversion of the argument passed to%TypedArray%.prototype.fill
in V8 ~ Chrome < 59, Safari < 14.1, FF < 55, Edge <=18 - Fixed some cases of
DeletePropertyOrThrow
in IE9- - Fixed the kind of error (
TypeError
instead ofError
) on incorrectexec
result inRegExp.prototype.test
polyfill - Fixed dependencies of
{ actual, full, features }/typed-array/at
entries - Added Electron 20.0 compat data mapping
- Added iOS Safari 15.5 compat data mapping
- Refactoring
v3.22.7
- Added a workaround for V8 ~ Chrome 53 bug with non-writable prototype of some methods, #1083
v3.22.6
- Fixed possible double call of
ToNumber
conversion on arguments ofMath.{ fround, trunc }
polyfills -
Array.prototype.includes
marked as fixed in FF102
v3.22.5
- Ensured that polyfilled constructors
.prototype
is non-writable - Ensured that polyfilled methods
.prototype
is not defined - Added detection and fix of a V8 ~ Chrome <103 bug of
struturedClone
that returnsnull
if cloned object contains multiple references to one error
v3.22.4
- Ensured proper
.length
of polyfilled functions even in compressed code (excepting some ancient engines) - Ensured proper
.name
of polyfilled accessors (excepting some ancient engines) - Ensured proper source /
ToString
conversion of polyfilled accessors - Actualized Rhino compat data
- Refactoring
v3.22.3
- Added a fix for FF99+
Array.prototype.includes
broken on sparse arrays
v3.22.2
- Fixed
URLSearchParams
in IE8- that was broken in the previous release - Fixed
__lookupGetter__
entries
v3.22.1
- Improved some cases of
RegExp
flags handling - Prevented experimental warning in NodeJS ~ 18.0 on detection
fetch
API - Added NodeJS 18.0 compat data
v3.22.0
-
Change
Array
by copy proposal:- Moved to Stage 3, March TC39 meeting
- Disabled forced replacement and added
/actual/
entry points for methods from this proposal -
Array.prototype.toSpliced
throws aTypeError
instead ofRangeError
if the result length is more thanMAX_SAFE_INTEGER
, proposal-change-array-by-copy/70
- Added some more
atob
/btoa
fixes:- NodeJS <17.9
atob
does not ignore spaces, node/42530 - Actual NodeJS
atob
does not validate encoding, node/42646 - FF26- implementation does not properly convert argument to string
- IE / Edge <16 implementation have wrong arity
- NodeJS <17.9
- Added
/full/
namespace as the replacement for/features/
since it's more descriptive in context of the rest namespaces (/es/
⊆/stable/
⊆/actual/
⊆/full/
) - Avoided propagation of removed parts of proposals to upper stages. For example,
%TypedArray%.prototype.groupBy
was removed from theArray
grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in/actual/
entries - but it should be available in early-stage entries to avoid breakage. - Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
- Bug fixes:
- Tooling:
- Stabilized proposals are filtered out from the
core-js-compat
->core-js-builder
->core-js-bundle
output. That mean that if the output contains, for example,es.object.has-own
, the legacy reference to it,esnext.object.has-own
, no longer added. - Aligned modules filters of
core-js-builder
andcore-js-compat
, now it'smodules
andexclude
options - Added support of entry points, modules, regexes, and arrays of them to those filters
- Missed
targets
option ofcore-js-compat
means that thetargets
filter just will not be applied, so the result will contain modules required for all possible engines
- Stabilized proposals are filtered out from the
- Compat data:
-
.stack
property onDOMException
marked as supported from Deno 1.15 - Added Deno 1.21 compat data mapping
- Added Electron 19.0 and updated 18.0 compat data mapping
- Added Samsung Internet 17.0 compat data mapping
- Added Opera Android 68 compat data mapping
-
v3.21.1
- Added a bugfix for the WebKit
Array.prototype.{ groupBy, groupByToMap }
implementation -
core-js-compat
targets parser transforms engine names to lower case -
atob
/btoa
marked as fixed in NodeJS 17.5 - Added Electron 18.0 compat data mapping
- Added Deno 1.20 compat data mapping
v3.21.0
- Added Base64 utility methods:
-
atob
-
btoa
-
- Added the proper validation of arguments to some methods from web standards
- Forced replacement of all features from early-stage proposals for avoiding possible web compatibility issues in the future
- Added Rhino 1.7.14 compat data
- Added Deno 1.19 compat data mapping
- Added Opera Android 66 and 67 compat data mapping
- Added iOS Safari 15.3 and 15.4 compat data mapping
v3.20.3
- Detects and replaces broken third-party
Function#bind
polyfills, uses only nativeFunction#bind
in the internals -
structuredClone
should throw an error if no arguments passed - Changed the structure of notes in
__core-js_shared__
date-fns/date-fns
v2.29.1
Thanks to @fturmel for working on the release.
Fixed
v2.29.0
On this release worked @tan75, @kossnocorp, @nopears, @Balastrong, @cpapazoglou, @dovca, @aliasgar55, @tomchentw, @JuanM04, @alexandresaura, @fturmel, @aezell, @andersravn, @TiagoPortfolio, @SukkaW, @Zebreus, @aviskarkc10, @maic66, @a-korzun, @Mejans, @davidspiess, @alexgul1, @matroskin062, @undecaf, @mprovenc, @jooola and @leshakoss.
Added
Fixed
-
Fixed long formatters in the South African English locale (
en-ZA
). -
Fixed weekday format for
formatRelative
in the Portuguese locale (pt
). -
Fixed issue parsing months in Croatian (
hr
), Georgian (ka
) and Serbian (sr
andsr-Latn
) locales.
Changed
cure53/DOMPurify
v2.3.10
- Added support for sanitization of attributes requiring Trusted Types, thanks @tosmolka
v2.3.9
- Made TAG and ATTR config options case-sensitive when parsing XHTML, thanks @tosmolka
- Bumped some dependencies, thanks @is2ei
- Included github-actions in the dependabot config, thanks @nathannaveen
v2.3.8
- Cleaned up a minor issue with the 2.3.7 release, thanks @johnbirds
No other changes compared to 2.3.7 release, which entail:
- Fixes around a bug in Safari, thanks @sybrew
- Slightly improved performance, thanks @tiny-ben-tran
- Lots of chores, bumps and typo fixes, thanks @is2ei
- Removed unnecessary string trimming, thanks @christopherehlen
v2.3.7
v2.3.6
- Added an option to allow HTML5 doctypes, thanks @tosmolka
- Bumped several dependencies, thanks @is2ei
- Updated documentation to cover recently added flags, thanks @is2ei
v2.3.5
- Performed several chores and cleanups, thanks @is2ei
- Fixed a bug when working with Trusted Types, thanks @tosmolka
- Fixed a bug with weird behavior on insecure nodes in IN_PLACE mode, thanks @tosmolka
- Added more SVG attributes to allow-list, thanks @rzhade3
markedjs/marked
v4.0.18
Bug Fixes
v4.0.17
Bug Fixes
v4.0.16
Bug Fixes
v4.0.15
Bug Fixes
v4.0.14
Bug Fixes
v4.0.13
Bug Fixes
v4.0.12
Bug Fixes
v4.0.11
Bug Fixes
jossef/material-design-icons-iconfont
v6.7.0
Features
- font: auto-update font from remote cdn (afde267)
v6.6.0
Features
v6.5.0
Features
v6.4.2
Bug Fixes
- semantic release git tag (70f03c6)
- rtl: do not override document direction (#87) (ac09ba9), closes #49
- removing "v" prefix from releases (98aa0a6)
v6.4.1
Bug Fixes
- removing "v" prefix from releases (98aa0a6)
v6.4.0
Features
- css version without codepoints (e37e3b3)
v6.3.0
Features
- css minified version + sourcemaps (7fc4cc9)
v6.2.0
Features
SortableJS/Sortable
v1.15.0
googlechrome/workbox
v6.5.4
What's New 👀
- Webpack plugin can be extended and subclasses can access the
config
property [#3056] - In
workbox-precaching
during a fall back to the network, if the request'smode
isno-cors
,integrity
will not be used and the cache entry will not be repaired. [#3099]
What's fixed 🐛
Misc 🤹
- updated
idb
andselenium-assitant
versions
Thank yous 🌿
- Thank you @DibyodyutiMondal & @theghostbel for your contributions!
Full Changelog: https://github.com/GoogleChrome/workbox/compare/v6.5.3...v6.5.4
v6.5.3
v6.5.2
Workbox v6.5.2 includes a number of improvements to the TypeScript documentation and exported types, which should in turn improve the generated documentation.
A full changelog is available at https://github.com/GoogleChrome/workbox/compare/v6.5.1...v6.5.2
v6.5.1
The Workbox v6.5.1 release includes a few changes related to our TypeScript interfaces and documentation.
A full changelog is available at https://github.com/GoogleChrome/workbox/compare/v6.5.0...v6.5.1
What's New
- Additional inline
@example
s of using our build tools have been added to the TSDocs forworkbox-build
andworkbox-webpack-plugin
. [#3038] - The TypeScript type for the
generateSW()
,injectManifest()
, andgetManifest()
methods inworkbox-build
has been updated fromunknown
to an appropriate actual type specific to each method. This should lead to better TSDoc generation and type inferences for developers. As this takes what was previously only a runtime check and moves it to a compile-time check, we believe that it should be functionally equivalent to prior releases, but if you run into problems, please let us know by opening an issue. [#3037]
What's Fixed
- We have re-added the
default
export toworkbox-webpack-plugin
. [#3036]
v6.5.0
The Workbox v6.5.0 release includes a number of smaller fixes, as well as a major rewrite of the workbox-webpack-plugin
to TypeScript.
A full changelog is available at https://github.com/GoogleChrome/workbox/compare/v6.4.2...v6.5.0
What's New
-
workbox-webpack-plugin
has been rewritten in TypeScript, and has public TypeScript definitions for its interfaces published as part of this release. We do not anticipate any changes in the underlying functionality as part of this rewrite. [#2882] - A
forceSyncFallback
parameter has been added toworkbox-background-sync
, without changing the default behavior. WhenforceSyncFallback
is explicitly set totrue
,workbox-background-sync
will always attempt to replay queued requests when the service worker starts up and never rely on thesync
event listener. Most developers will not need this behavior, but it can be useful when targeting environments that have a non-functional Background Sync implementation, like some Electron runtimes. [#3020]
What's Fixed
- A more informative message is returned when an opaque response is erroneously used in
workbox-streams
. [#3001] - Removed a dynamic method call in
workbox-background-sync
which could lead to errors when run through with certain aggressive minifiers. [#3012] - A
waitUntil()
was added to theStaleWhileRevalidate
strategy, ensuring that it works properly with navigation preload responses. [#3015] - Removed the dependency on the deprecated
source-map-url
package. [#3031]
New Contributors
Thank you to @roikoren755 for their contributions to the workbox-webpack-plugin
TypeScript migration!
v6.4.2
The Workbox v6.4.2 release fixes a few issues:
What's Changed
- fix: update
@apideck/better-ajv-errors
to ^0.3.1 by @wopian in https://github.com/GoogleChrome/workbox/pull/2988 - Fix request vs. response in
ExpirationPlugin
docs by @mungojam in https://github.com/GoogleChrome/workbox/pull/2987 - Skip ignoreURLParametersMatching in
workbox wizard --injectManifest
by @jeffposnick in https://github.com/GoogleChrome/workbox/pull/2992
New Contributors
- @wopian made their first contribution in https://github.com/GoogleChrome/workbox/pull/2988
- @mungojam made their first contribution in https://github.com/GoogleChrome/workbox/pull/2987
Full Changelog: https://github.com/GoogleChrome/workbox/compare/v6.4.1...v6.4.2
v6.4.1
The Workbox v6.4.1 release fixes a few issues:
🐛 What's Fixed?
workbox-build
- The dependency on
@apideck/better-ajv-errors
has been updated, which in turn addresses a security issue in one of its dependencies. [#2977]
worbox-navigation-preload
- The inline TypeScript definition for
preloadResponse
was incorrect, and has been fixed to reflect the previous definition that used to be provided by the TypeScript standard library. [#2975]
worbox-strategies
- Take
request.url
into account inStrategyHandler.getCacheKey()
. This ensures if a custom strategy overrides theStrategy._handle()
method and performs multiple cache operations on different URLs, the cache key is properly calculated for each distinct URL. [#2973]
v6.4.0
Workbox v6.4.0 includes:
🎉 What's New?
- We upgraded to TypeScript 4.4.3. This required us to declare inline some types that are now longer par
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication