Update dependencies and reduce cache duration #3496
Conversation
|
Can you fix #3302 while we're at it? |
|
I was not sure if they all should be or the ones that make sense to be changed? |
Co-authored-by: Federico <me@fregante.com>
| @@ -61,13 +61,13 @@ | |||
| "shorten-repo-url": "^2.0.0", | |||
There was a problem hiding this comment.
How come mem wasn't updated? There's 6.1.0
I generally use to check what's available and update all sub-dependencies correctly. npm still can't be trusted with the lock
npx npm-check -u && rm -rf node_modules package-lock.json && npm install && npm run testThere was a problem hiding this comment.
You said you did not want to update it
I actually had left this on 6.0.1 because it's technically a better version since we don't use
mem.clearOriginally posted by @fregante in #3168 (comment)
There was a problem hiding this comment.
Yeah, because I thought that 6.1.0 was the most recent feature, but the "worse version" still hasn't been published yet sindresorhus/memoize#58 (comment)
You can use 6.1.0 now
| "ts-node": "^9.0.0", | ||
| "type-fest": "^0.16.0", | ||
| "typescript": "^4.1.0-dev.20200810", | ||
| "typescript": "^4.0.2", |
There was a problem hiding this comment.
We're going back? I want to make sure that the reason why this was added has been solved in v4. Tonight I have no data left though
There was a problem hiding this comment.
I checked I get no messages. I put it on the latest stable version. want me to check the latest dev version?
Tonight I have no data left though
You run on limited data?? - Wow
There was a problem hiding this comment.
You run on limited data?? - Wow
WiFi wasn't working and promptly ran out of 4G data 🤣
fregante
left a comment
fregante
left a comment
There was a problem hiding this comment.
The rest of the times looks fine
source/features/highlight-collaborators-and-own-conversations.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Federico <me@fregante.com>
fregante
changed the title
2 participants
Fixes #3302
#3489 (comment)