Skip to content

Instantly share code, notes, and snippets.

🌴
Vacation, back on 22nd Jul 2019

Dominik Wilkowski dominikwilkowski

🌴
Vacation, back on 22nd Jul 2019
Block or report user

Report or block dominikwilkowski

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@dominikwilkowski
dominikwilkowski / README.md
Last active Feb 22, 2019 — forked from evangs/delete-old-files.js
Batch delete old files from Slack
View README.md

Batch delete old file from your slack workspace

Freeing space

To free up some space in your slack workspace and having to delete each file by hand

To run the app you first need a legacy token from slack for your workspace. Then download the cleanSlack.js file and run it via Node.js.

By default the script will delete files older than a year. You can change that in the TIMESTAMP variable.

@dominikwilkowski
dominikwilkowski / service-workers.md
Created Sep 5, 2018 — forked from Rich-Harris/service-workers.md
Stuff I wish I'd known sooner about service workers
View service-workers.md

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

You can’t perform that action at this time.