mui-x
mui-x copied to clipboard
mui
Bump lru-cache to ^10.2.2
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| lru-cache | ^7.18.3 -> ^10.2.2 |
Release Notes
isaacs/node-lru-cache (lru-cache)
v10.2.2
v10.2.1
v10.2.0
- types: implement the
Map<K, V>interface
v10.1.0
- add
cache.info(key)to get value as well as ttl and size information.
v10.0.3
v10.0.2
v10.0.1
v10.0.0
cache.fetch()return type is nowPromise<V | undefined>instead ofPromise<V | void>. This is an irrelevant change practically speaking, but can require changes for TypeScript users.
v9.1.2
v9.1.1
v9.1.0
cache.set(key, undefined)is now an alias forcache.delete(key)
v9.0.3
v9.0.2
v9.0.1
v9.0.0
- Use named export only, no default export.
- Bring back minimal polyfill. If this polyfill ends up being used, then a warning is printed, as it is not safe for use outside of LRUCache.
v8.0.5
v8.0.4
v8.0.3
v8.0.2
v8.0.1
v8.0.0
- The
fetchContextoption was renamed tocontext, and may no longer be set on the cache instance itself. - Rewritten in TypeScript, so pretty much all the types moved around a lot.
- The AbortController/AbortSignal polyfill is removed. For this reason, Node version 16.14.0 or higher is now required.
- Internal properties were moved to actual private class properties.
- Keys and values must not be
nullorundefined. - Minified export available at
'lru-cache/min', for both CJS and MJS builds.
Configuration
📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy preview: https://deploy-preview-11843--material-ui-x.netlify.app/
Generated by :no_entry_sign: dangerJS against 97c451de08e373c787742e9b60356d6d902ad9de
This pull request has conflicts, please resolve those before we can evaluate the pull request.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
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.
WDYT @mui/code-infra, does having es5 as the TS target make sense at this point? 🤔 🤷
https://app.circleci.com/pipelines/github/mui/mui-x/60171/workflows/97392b3b-a07f-456f-a2ac-6d5bcbfdc867/jobs/343575
It's blocking this PR. 🤔
does having es5 as the TS target make sense at this point?
Isn't this only relevant if we're compiling to js with tsc? We use babel + preset-env, I suppose this setting doesn't change anything. I guess you could try diffing the compiled output with different values to verify.
Isn't this only relevant if we're compiling to js with
tsc? We use babel + preset-env, I suppose this setting doesn't change anything. I guess you could try diffing the compiled output with different values to verify.
Indeed, our typing compilation is done with a different process than tsc. 🤔
I've done some preliminary testing and it seems that there are no build package changes.
The only observable change is a shorter build time as we need less transpilation. 👍
@Janpot Would you suggest making the change in the monorepo for every downstream package to take effect?
Or only mui-x? 🤔
@Janpot Would you suggest making the change in the monorepo for every downstream package to take effect?
Yes, I think hat makes sense. 👍
Waiting for @mui/monorepo to be bumped in order to avoid the need for explicit target: https://github.com/mui/mui-x/pull/11843/commits/7b611188a1cb8fe850e9c987d4d860b89229939a
This pull request has conflicts, please resolve those before we can evaluate the pull request.