-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace update-notifier #61
Conversation
@olore some pointers wrt your remaining items, in case it helps:
const cacache = require('cacache')
const cache = path.join(npm.config.get('cache'), '_cacache') // I know, it's weird. It'll be better soon.
// writing
cacache.put(cache, 'update-notifier:last-check', Date.toUTCString()).then(....)
// reading
cacache.get(cache, 'update-notifier:last-check').then(time => {
console.log('last check time was', new Date(time.toString('utf8')))
})
|
Thanks @zkat ! This will definitely help.
I feel like I am just missing something simple 😃 |
90db349
to
228abd0
Compare
228abd0
to
9902590
Compare
I think I got everything, it's ready for review. I still don't think I properly removed update-notifier (it's still in node_modules). Any pointers are appreciated. |
Would it be possible to have a way to make sure that this doesn't get run, similar to how the |
@ewanharris - yes the previous flag is still supported |
I don't know how to successfully complete the final task (I created for myself!) If so, this should be good to go. Let me know if there is anything else to do here. |
Hey, sorry for taking so long to get back to this. I have one last request: Can you write a basic test for this? I realize it's gotten big enough that I'm anxious about merging without at least a basic stability check. |
@zkat yes I will see what I can do. Back when I started this, I was looking for any tests in this area and came up empty. I'll give it another look. Thanks. |
a40ed02
to
f6c6883
Compare
@olore we're going to address this in |
@darcyclarke it's all good! Thanks for the link to the new issue |
See discussion on npm community
bundleDependencies
I tested this by changing package.json version to 6.3.0 :