FightForSub / ffs-zera

Fight For Subs Front
https://ffs-events.zerator.com/
GNU General Public License v3.0
27 stars 9 forks source link

chore(deps): update dependency localforage to v1.10.0 #153

Open renovate[bot] opened 3 years ago

renovate[bot] commented 3 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
localforage 1.7.3 -> 1.10.0 age adoption passing confidence

Release Notes

localForage/localForage ### [`v1.10.0`](https://togithub.com/localForage/localForage/blob/HEAD/CHANGELOG.md#​1100-httpsgithubcomlocalForagelocalForagereleasestag1100) [Compare Source](https://togithub.com/localForage/localForage/compare/1.9.0...1.10.0) - Avoid uncaught error in `dropInstance`. You can now catch errors thrown by `dropInstance`, see [#​807](https://togithub.com/localForage/localForage/issues/807). ### [`v1.9.0`](https://togithub.com/localForage/localForage/blob/HEAD/CHANGELOG.md#​190-httpsgithubcommozillalocalForagereleasestag190) [Compare Source](https://togithub.com/localForage/localForage/compare/1.8.1...1.9.0) - Fixed TypeScript definition for `getItem`. It now notes that `getItem` can return `null`, so this change may cause TypeScript code that didn't account for `null` values to fail. See [#​980](https://togithub.com/localForage/localForage/issues/980). ### [`v1.8.1`](https://togithub.com/localForage/localForage/blob/HEAD/CHANGELOG.md#​181-httpsgithubcommozillalocalForagereleasestag181) [Compare Source](https://togithub.com/localForage/localForage/compare/1.8.0...1.8.1) - Reverted the ESM/`module` field change in [#​940](https://togithub.com/localForage/localForage/issues/940), which broke many builds. See: [#​979](https://togithub.com/localForage/localForage/issues/979). Sorry about that! 😓 ### [`v1.8.0`](https://togithub.com/localForage/localForage/blob/HEAD/CHANGELOG.md#​180-httpsgithubcommozillalocalForagereleasestag180) [Compare Source](https://togithub.com/localForage/localForage/compare/1.7.4...1.8.0) - No changes to code, but added a `module` field in `package.json` for better ESM support. See: [#​940](https://togithub.com/localForage/localForage/issues/940). ### [`v1.7.4`](https://togithub.com/localForage/localForage/blob/HEAD/CHANGELOG.md#​174-httpsgithubcommozillalocalForagereleasestag174) [Compare Source](https://togithub.com/localForage/localForage/compare/1.7.3...1.7.4) - Use `openKeyCursor` instead of `openCursor` for `key()` retrieval. Props to [@​MeMark2](https://togithub.com/MeMark2) for the fix, and thanks to [@​lincolnthree](https://togithub.com/lincolnthree) and [@​f](https://togithub.com/f) for additional testing!

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 2 years ago

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

The artifact failure details are included below:

File name: package-lock.json
npm ERR! Linux 4.15.0-1050-aws
npm ERR! argv "/usr/local/node/14.18.1/bin/node" "/home/ubuntu/.npm-global/bin/npm" "install" "--package-lock-only" "--no-audit" "--ignore-scripts"
npm ERR! node v14.18.1
npm ERR! npm  v3.10.10

npm ERR! cb.apply is not a function
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/renovate/gh/FightForSub/ffs-zera/npm-debug.log
renovate[bot] commented 1 year ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.